| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Fix for: Shared object "libprotobuf.so.28" not found
|
|
its buildlink3.mk now includes openssl's buildlink3.mk
|
|
Version 3.12.1 fixes a number of bugs:
- Fixed a bug that caused a multi-document transaction to fail when the first
operation was large bulk write (>48MB) that required splitting a batched
write command (`PYTHON-2915`_).
- Fixed a bug that caused the ``tlsDisableOCSPEndpointCheck`` URI option to
be applied incorrectly (`PYTHON-2866`_).
|
|
Changes in MySQL 5.7.36
Security Notes
Bugs Fixed
Security Notes
The linked OpenSSL library for MySQL Server has been updated to version 1.1.1l. Issues fixed in the new OpenSSL version are described at https://www.openssl.org/news/cl111.txt and and http://www.openssl.org/news/vulnerabilities.html.
Bugs Fixed
Incompatible Change: For all SELECT statements on a view, the query digest was based on the view definition. As a result, different queries had the same digest and aggregated together in the Performance Schema table events_statements_summary_by_digest, so statistics in that table were not usable for distinguishing distinct SELECT statements.
The query digest for each SELECT statement on a view now is based on the SELECT, not the view definition. This enables distinguishing distinct SELECT statements in the events_statements_summary_by_digest table. However, tools that use query digests may need some adjustment to account for this change. For example, MySQL Enterprise Firewall and query rewrite plugins rely on query digests and existing rules for them that are associated with views may need to be updated.
InnoDB: With undo log truncation enabled (innodb_undo_log_truncate=ON), it was possible for a deadlock and eventual failure to occur when an undo log truncate operation was initiated after a version upgrade from MySQL 5.6 to MySQL 5.7.34 or earlier. A patch introduced in MySQL 5.7.35
[Note] InnoDB: Found duplicate reference rseg: 33 space: 1 page: 3
[Note] InnoDB: Reset pre-5.7.2 rseg: 1 after duplicate is found.
If pre-5.7.2 rollback segment slots have no undo data to purge, a message similar to the following is emitted:
[Note] InnoDB: Successfully reset 32 pre-5.7.2 rseg slots.
If undo data is found in pre-5.7.2 rollback segment slots, a message similar to the following is emitted recommending a slow shutdown and restart:
[Note] InnoDB: pre-5.7.2 rseg: 2 holds data to be purged.
History length: 1. Recommend slow shutdown with innodb_fast_shutdown=0 and restart
InnoDB: Truncation of an undo tablespace during use by an active transaction raised an assertion failure. The transaction was prematurely marked as complete, permitting the truncation operation.
InnoDB: Deleting or updating a row from a parent table initiated a cascading SET NULL operation on the child table that set a virtual column value to NULL. The virtual column value should have been derived from the base column value.
Thanks to Yin Peng at Tencent for the contribution.
InnoDB: The InnoDB recovery process did not recognize that page compression had been applied to data that was being recovered, causing the tablespace data file to increase in size during the redo log apply phase, which could lead to a recovery failure for systems approaching a disk-full state.
Replication: The error messages issued by MySQL Replication when GTIDs required for auto-positioning have been purged could be incorrectly assigned or scrambled in some situations.
Replication: The contents of the gtid_executed and gtid_purged GTID sets were not persisted after restoring a dump taken using mysqldump. The dump file sequence has now been changed so that the mysql schema (which contains the mysql.gtid_executed table) is not dropped after the gtid_purged GTID set is written. A new option --skip-mysql-schema is added for mysqldump which lets you choose not to drop the mysql schema at all.
JSON: Conversion of JSON values to text caused linear growth of the destination string, resulting in an unnecessarily high number of reallocations. Now this process uses exponential growth instead, to reduce the number of allocations required.
This fix originally appeared in MySQL 8.0 and was backported to MySQL 5.7 by Annirudh Prasad, whom we thank for the contribution.
Concurrent insert operations on multiple tables with full-text indexes caused a large number of full-text index synchronization requests, resulting in an out of memory condition.
When a query uses a temporary table for aggregation, the group by item is used as a unique constraint on the temporary table: If the item value is already present, the row is updated; otherwise, a new row is inserted into the temporary table. If the item has a result field or reference item, it it evaluated twice, once to check whether the result exists in the temporary table and, if not, again while constructing the row to be inserted. When the group by item was nondeterministic, the result value used to check for existence differed from that with which an insert was attempted, causing the insert to be rejected if the value already existed in the table.
We fix this by using the hash of any nondeterministic items as the unique constraint, so that the hash is evaluated once only.
Quote handling was improved for the SHOW GRANTS statement.
|
|
Bump PKGREVISION.
|
|
|
|
0.48.8:
Unknown changes
|
|
Bump PKGREVISION
|
|
OpenLDAP 2.5.8 Release (2021/10/11)
Fixed libldap ldap_int_tls_connect: isdigit() requires unsigned char
Fixed libldap memory leak in ldap_get_option LDAP_OPT_X_TLS_PEERCERT
Fixed slapd to allow normalized values for namingContexts in cn=monitor
Fixed slapd to normalize the suffix in rootDSE
Fixed slapd slapadd to avoid destroying configDB prematurely
Fixed slapd to not spam logs with lastbind information
Fixed slapd slaptest migration to correctly set olcTSLVerifyClient
Fixed slapd-mdb multival delete handling
Fixed slapd-sql ldap_entry_objectclass table for mariadb/mysql
Fixed slapd-wt multiple issues
Fixed slapd-wt to close cache db correctly
Fixed slapo-ppolicy to restore OpenLDAP 2.4 compatibilty
Fixed slapo-syncprov to free uuid list when finished replaying sessionlog
Build
Fixed libldap result.c compilation on musl systems
Fixed slapd duplicate definition of peerbv
Fixed test suite with memberof modular builds
Contrib
Added man page for ppm contrib module
Fix crash when pwdCheckModuleArg is not defined for ppm
Documentation
Fixed guide download link for heimdal
Fixed guide documentation for TLSECName
Fixed guide documentation missing tags
Fixed guide loadbalancer typo
Fixed guide synprov-nopresent redundant text
Fixed guide various typos and fix config alignment
Removed ppolicy.schema from servers/slapd/schema/README
Fixed slapd.conf(5)/slapd-config(5) to document default for database monitoring
Fixed slapd-meta(5)/slapd-asyncmeta(5) verbiage for try-propagate
Fixed slapo-syncprov(5) to note entryCSN indexing is highly recommended
|
|
repmgr 5.3.0 is a major release.
This release provides support for PostgreSQL 14, released in September 2021.
A.1.1. Improvements
repmgr standby switchover: Improve handling of node rejoin failure on the demotion candidate.
Previously repmgr did not check whether repmgr node rejoin actually succeeded on the demotion candidate, and would always wait up to node_rejoin_timeout seconds for it to attach to the promotion candidate, even if this would never happen.
This makes it easier to identify unexpected events during a switchover operation, such as the demotion candidate being unexpectedly restarted by an external process.
Note that the output of the repmgr node rejoin operation on the demotion candidate will now be logged to a temporary file on that node; the location of the file will be reported in the error message, if one is emitted.
repmgrd: at startup, if node record is marked as "inactive", attempt to set it to "active".
This behaviour can be overridden by setting the configuration parameter repmgrd_exit_on_inactive_node to true.
repmgr node rejoin: emit rejoin target note information as NOTICE.
This makes it clearer what repmgr is trying to do.
repmgr node check: option --repmgrd added to check repmgrd status.
Add %p event notification parameter providing the node ID of the former primary for the repmgrd_failover_promote event.
A.1.2. Bug fixes
repmgr standby clone: if using --replication-conf-only on a node which was set up without replication slots, but the repmgr configuration was since changed to use_replication_slots=1, repmgr will now set slot_name in the node record, if it was previously empty.
repmgrd: rename internal shared library functions to minimize the risk of clashes with other shared libraries.
This does not affect user-facing SQL functions. However an upgrade of the installed extension version is required.
repmgrd: ensure short option -s is accepted.
|
|
5.2.0 (2021-10-03)
=====================
Features
- 1. Added support Python 3.10
2. Started shipping platform-specific wheels with the ``musl`` tag targeting typical Alpine Linux runtimes.
3. Started shipping platform-specific arm64 wheels for Apple Silicon.
Bugfixes
- Fixed pure-python implementation that used to raise "Dictionary changed during iteration" error when iterated view (``.keys()``, ``.values()`` or ``.items()``) was created before the dictionary's content change.
|
|
|
|
Upstream changes:
0.57 2021-09-27
- `$conn->dsn` and `$conn->driver_name` accessors
- Use of ExtUtils::MakeMaker instead of Module::Build
- Corrected, reduced, properly declared prerequisites
- POD tests in `xt/`
- Simplified SQLite version check
- Doc typo fix. Thanks to Michael R. Davis
|
|
... for packages where the go-module.mk defaults DTRT as-is.
|
|
Found by pkglint 21.3.1.
|
|
|
|
PostgreSQL 14 contains many new features and enhancements, including:
Stored procedures can now return data via OUT parameters.
The SQL-standard SEARCH and CYCLE options for common table expressions have been implemented.
Subscripting can now be applied to any data type for which it is a useful notation, not only arrays. In this release, the jsonb and hstore types have gained subscripting operators.
Range types have been extended by adding multiranges, allowing representation of noncontiguous data ranges.
Numerous performance improvements have been made for parallel queries, heavily-concurrent workloads, partitioned tables, logical replication, and vacuuming.
B-tree index updates are managed more efficiently, reducing index bloat.
VACUUM automatically becomes more aggressive, and skips inessential cleanup, if the database starts to approach a transaction ID wraparound condition.
Extended statistics can now be collected on expressions, allowing better planning results for complex queries.
libpq now has the ability to pipeline multiple queries, which can boost throughput over high-latency connections.
|
|
1.0.2:
Announcing Hiredis v1.0.2, which fixes CVE-2021-32765 but returns the SONAME to the correct value of 1.0.0.
|
|
|
|
- Python 3 support
- bug fixes
|
|
1.0.1
Fix for CVE-2021-32765 commit
|
|
Redis 6.2.6
Upgrade urgency: SECURITY, contains fixes to security issues.
Security Fixes:
* (CVE-2021-41099) Integer to heap buffer overflow handling certain string
commands and network payloads, when proto-max-bulk-len is manually configured
to a non-default, very large value [reported by yiyuaner].
* (CVE-2021-32762) Integer to heap buffer overflow issue in redis-cli and
redis-sentinel parsing large multi-bulk replies on some older and less common
platforms [reported by Microsoft Vulnerability Research].
* (CVE-2021-32687) Integer to heap buffer overflow with intsets, when
set-max-intset-entries is manually configured to a non-default, very large
value [reported by Pawel Wieczorkiewicz, AWS].
* (CVE-2021-32675) Denial Of Service when processing RESP request payloads with
a large number of elements on many connections.
* (CVE-2021-32672) Random heap reading issue with Lua Debugger [reported by
Meir Shpilraien].
* (CVE-2021-32628) Integer to heap buffer overflow handling ziplist-encoded
data types, when configuring a large, non-default value for
hash-max-ziplist-entries, hash-max-ziplist-value, zset-max-ziplist-entries
or zset-max-ziplist-value [reported by sundb].
* (CVE-2021-32627) Integer to heap buffer overflow issue with streams, when
configuring a non-default, large value for proto-max-bulk-len and
client-query-buffer-limit [reported by sundb].
* (CVE-2021-32626) Specially crafted Lua scripts may result with Heap buffer
overflow [reported by Meir Shpilraien].
Bug fixes that involve behavior changes:
* GEO* STORE with empty source key deletes the destination key and return 0
Previously it would have returned an empty array like the non-STORE variant.
* PUBSUB NUMPAT replies with number of patterns rather than number of subscriptions
This actually changed in 6.2.0 but was overlooked and omitted from the release notes.
Bug fixes that are only applicable to previous releases of Redis 6.2:
* Fix CLIENT PAUSE, used an old timeout from previous PAUSE
* Fix CLIENT PAUSE in a replica would mess the replication offset
* Add some missing error statistics in INFO errorstats
Other bug fixes:
* Fix incorrect reply of COMMAND command key positions for MIGRATE command
* Fix appendfsync to always guarantee fsync before reply, on MacOS and FreeBSD (kqueue)
* Fix the wrong mis-detection of sync_file_range system call, affecting performance
CLI tools:
* When redis-cli received ASK response, it didn't handle it
Improvements:
* Add latency monitor sample when key is deleted via lazy expire
* Sanitize corrupt payload improvements
* Delete empty keys when loading RDB file or handling a RESTORE command
|
|
(beta) Support for downsampling using continuous aggregate
(Experimental) Support for storage of exemplars
Performance improvements
Support of Thanos Store API
|
|
The 2.30 release brings performance improvements and bugfixes.
|
|
Fixes the bug that broke background workers, and some other minor things.
|
|
Build 127 (2020-08-22)
Bug fixes
- It was no longer possible to run GRANT or REVOKE statements.
Build 126 (2020-08-09)
Enhancements
- WbExport will now abort if a text export is started without a quote character but a quote character would be needed.
- For PostgreSQL, subscriptions and publications for logical replication are now shown in the DbTree and DbExplorer.
- For PostgreSQL, the attribute of IDENTITY REPLICA is now shown in the generated DDL.
- "Make uppercase" and "Make lowercase" now also work if no text is selected. In that case, (only) the character at the cursor is changed
- Passwords can now securely be encrypted using a master password. The old password encryption is no longer supported.
- The properties base profile storage (wb-profiles.properties) is now the default. The old XML format is still supported.
- WbVarDef now supports conditional execution.
- WbCopy now supports views as the source by using -includeViews=true.
- The result panel is now automatically displayed if it was minimized before running a statement.
- It's now possible to configure italic and bold for syntax highlighting
- For SQL Server, partitioning information about a table is now included in the generated DDL
- WbImport can now import all sheets of a spreadsheet into the same table when -sheetName=* is specified together with -table
- The annotation @WbResultAsText can now be used to turn the "text mode" display on for multiple statements
- For PostgreSQL, the "match mode" of foreign key constraints is now displayed and included in the generated DDL
- A new Windows launcher is available that removes the need for a separate 64 and 32 bit executables and can optionally download a JRE
- It's now possible to optionally open the saved file when using "Save As"
- It's now possible to use a special variable in WbImport to assign the input file's line number to a column.
- It's now possible to cycle through the result tabs using a keyboard shortcut.
- When exporting a single table from the table list (Database Explorer or DbTree) it's now possible to select the columns to export.
- It's now possible to display results in GUI mode as "text" in the messages area.
- It's now possible to define a SQL expression to be used in the INSERT statement that WbImport uses to apply SQL functions on the input value.
- Selecting foreign key values is now also supported for DELETE statements.
- The list of shortcut keys can now be exported (with the usual "Save As" formats)
- Invoking code completion in the WHERE clause without a column now displays all columns of all used tables of the query
- For MySQL and MariaDB versions that support them, check constraints are now shown in the generated DDL
- Recently opened files are now accessible through the "File" menu.
- For PostgreSQL, default values on columns of views are now shown in the generated DDL
- For HSQLDB 2.5, the new options for temporal tables are now shown in the generated DDL
- Added new command WbSetSchema to change the current schema using the driver's JDBC API
- For PostgreSQL 12, the new computed columns are now shown in the generated DDL
- The tooltip of a column header now always includes the table name if available
Bug fixes
- For Redshift, tables sources were not always displayed
- When using WbImport with mode=upsert and a table that has a multi-column primary key, the wrong MERGE statement was generated for SQL Server, HSQLDB and DB2
- When exporting to ODS, the generated files could not be opened with Microsoft Excel.
- Using nested WbIncludes failed with an exception
- When invoking code-completion in the ON part of a JOIN, not tables where shown.
- When selecting a global SSH configuration for a connection profile, it was no longer possible to revert to a "non-global" configuration
- When specifying a SSH Tunnel without a password and no keyfile, SQL Workbench did not prompt for the password
- For WbCopy, when using -createTarget=true together with -targetSchema the new table was created in the wrong schema
- Fixed an issue when loading the SQL Server JDBC driver with certain versions of OpenJDK
- For SQL Server, when including the CREATE TABLE statement in the output when exporting data as SQL the export failed
- WbDataDiff did not work properly if the key columns contained NULL values.
- When exporting or saving data, it was not possible to enter the filename manually into the dialog.
- Month names were case sensitive when using -dateFormat or -timestampFormat with WbImport
- For Oracle 18c and later, index information wasn't displayed correctly.
- For Oracle 18c and later, DDL for identity columns wasn't generated correctly.
- For Oracle, the generated IGNORE_DUP_KEY hint was incorrect if the order of the PK columns was different to the column order of the table.
- Assigning multiple variables with WbVarDef was not possible if -variable was used.
- For Redshift, finding tables on the search path was no longer working.
- For PostgreSQL, using the JDBC driver 42.2.11, the value for columns defined as "timestamp with time zone" could not be retrieved any longer.
- The cursor position wasn't calculated correctly, if real tabs where used in the editor (regression from 125.6)
- Sorting columns defined as arrays in the result did not work properly.
- The new Windows launcher (introduced in 125.5) did not work if run from a directory with spaces in the name
- Fixed some problems with the cursor position in the editor with High-DPI displays (on Windows)
- For PostgreSQL, the DDL for partitioned tables with sub-partitions was not generated correctly
- Using WbImport with temp tables as the target did not work with PostgreSQL and SQL Server
- When using UCanAccess certain types of "linked columns" are now displayed correctly.
- For DB2 on AS/400 the CSID attribute was also generated for data types where it wasn't relevant.
- Individual statements were not detected correctly in the editor if the text started with a semicolon.
- "Create SQL List" did not work properly if only a part of the first or last line was selected.
- For PostgreSQL, the dependency display of trigger functions wasn't working any more.
- When using Page Down when the editor text was shorter than the number of lines, the display was corrupted.
- When closing the macro dialog while macros were filtered, only the visible macros were saved.
- For PostgreSQL, check constraints and default values were no longer displayed correctly in the generated DDL
- For XLSX exports, using -infoSheet did not work any longer
- When using -endRow with WbImport, the following rows weren't exported, but the input file was still read until the end
- Filtering the list of macros did no longer work correctly.
- For SQLite, all values are now retrieved as strings to workaround problems with the lack of explicit data types.
- Common table expressions containing DML are now correctly identified when the "Read Only" option is selected in the connection profile.
- The XML file generated by WbSchemaDiff was incorrect when multiple views need to be dropped.
- The SQL formatter removed trailing semicolons if only a single statement was formatted.
- Fractional seconds were not correcly formatted in timestamp literals in generated SQL statements.
- When editing a result with columns from multiple tables where the columns were not fully qualified, an exception occurred rather than a usable error message.
- Conditional execution of Workbench commands using -ifDefined and -ifNotDefined behaved the same as -ifEmpty and -ifNotEmpty
- For Postgres, infinity values for timestamp with time zone could not be read from the database.
- If the JDBC driver returned LocalDateTime or LocalDate values, those weren't formatted properly in SQL statements or text files.
Build 125 (2019-05-08)
Enhancements
- All additional libraries are now expected in the directory "ext".
- In the DbExplorer, using "Show Rowcounts", now displays the row counts as a new column in the table list.
- WbDataDiff now also supports -clobAsFile when generating SQL statements
- For WbExport and WbDataDiff -clobFileThreshold has been added
- For MariaDB 10.3, sequences are now displayed in the DbExplorer
- The "Manage Macros" dialog now also supports filtering of the macros.
- For Oracle, the generated DDL for tables now contains the definitions of extended column statistics.
- It's now possible to control the behaviour of WbDefineVar when NULL values are retrieved through a SQL query
- It's now possible to specify a message with WbEcho that is displayed even if verbose logging was turned off (e.g. using -verbose=false for WbInclude)
- For WbExport and WbImport, it's now possible to define the values for -quoteChar and -delimiter using unicode escape notation (e.g. \0008)
- WbDefineVar now supports the -silent option so suppress the details about the defined variable
- For conditional execution of some SQL Workbench/J commands, checking for the (non) existence of files or tables is now supported
- For Postgres, comments on foreign key constraints are now displayed in the DbExplorer and the generated DDL source
- Confirmation to close "Other tabs" can now be configured separately.
Bug fixes
- For SQL Server, DateTime values were not displayed correctly
- For Oracle the source of materialized views using ON PREBUILT TABLE was incorrect.
- Relative file names were treated differently by the SQL Workbench commands and the ifFileExists check.
- For MySQL, the source of triggers wasn't displayed.
- Copy to clipboard did not use the format string for decimal values
- For Oracle, using -mode=upsert with CLOB columns did not work for WbImport
- For some JDBC drivers, the console did not display the column's alias, but the real column name in a result
- For Postgres, nesting dollar quoted strings did not work.
- When retrieving XML columns using a driver that supports the JDBC API getXML() NULL values would result in an error.
- For Postgres, the generated source for an extension in the DbExplorer was not correct.
- The detection of the DB2 version was no long working correctly
- Numbers that can't be stored in Excel's file format are now exported as strings rather than numbers
- For Oracle, certain timestamp values were incorrectly exported.
- For Oracle 12, statements using "WITH FUNCTION" or "/*+ WITH_PLSQL */" to create inline PL/SQL functions could not be executed.
- WbCall did not display values for OUT parameters for all data types.
- For Oracle, the status of foreign keys (enabled, validated) was no longer displayed in the DbExplorer.
- For PostgreSQL, retrieving the policies for row level security was not working for versions prior to 10 any more.
- When using -profileStorage wih a filename without a path, files located in the config directory where not found
- Generating a SQL script using WbDataDiff on tables with timestamptz columns in Postgres did not work
|
|
|
|
|
|
5.48.0 (2021-09-01)
* Make the unused_associations plugin association reflection tracking work
correctly when combining coverage runs (jeremyevans)
* Add Database#like_without_collate on MSSQL, to avoid using COLLATE on LIKE
arguments, which can significantly improve performance (jeremyevans)
* Add Model::Errors#full_message private method for easiest i18n support for
errors with multiple attributes (jeremyevans) (#1779)
|
|
|
|
|
|
|
|
|
|
Cross-platform TUI database management tool written in Rust.
Features:
- Cross-platform support (macOS, Windows, Linux)
- Multiple Database support (MySQL, PostgreSQL, SQLite)
- Intuitive keyboard only control
|
|
macOS build.
|
|
1.4.5:
Unknown changes
|
|
As of MySQL 5.7, installations created using --initialize no longer
have an empty root password; one is generated as part of the process
and marked expired. (This message is in part simply advice to read the
documentation. However, it's possible other downstream packagers use
--initialize-insecure instead, which retains the old empty password
approach, so this could be a pkgsrc-specific detail to consider.)
|
|
Version 1.21, 2021-09-02
* Crash tolerance
By default it is possible for an abrupt crash (e.g., power failure,
OS kernel panic, or application process crash) to corrupt the gdbm
database file. A new Linux-only mechanism enables applications to
recover the database state corresponding to the most recent
successful gdbm_sync() call before the crash. See the chapter 17
"Crash Tolerance" in the GDBM manual.
* New database file format: numsync
The new "numsync" database format is designed to better support
crash tolerance. To create a database in numsync format, the gdbm_open
(or gdbm_fd_open) function must be given the GDBM_NEWDB|GDBM_NUMSYNC
flags. The GDBM_NUMSYNC flag also takes effect when used together
with GDBM_WRCREAT, provided that the new file is created.
New function gdbm_convert() is provided for converting the databases
from standard GDBM format to numsync and vice versa.
The gdbmtool tool can also be used for converting databases between
these two formats.
* Changes in gdbmtool
** Fix string output in non-ASCII encodings
Printable multi-byte sequences are correctly represented on output.
This also fixes octal representation of unprintable characters.
** The filename variable
This variable supplies the name of database file for use in "open"
command, if the latter is called without arguments. If "open" is
called with the file name argument, the "filename" variable is
initialized to this value.
** The fd variable
If set, its value must be an open file descriptor referring to a
GDBM database file. The "open" command will use gdbm_fd_open
function to use this file. Upon closing the database, this
descriptor will be closed and the variable will be unset.
The file descriptor to use can also be supplied using the
-d (--db-descriptor) command line option.
** The format variable
Defines the format in which new databases will be created. Allowed
values are: "standard" (default) and "numsync".
** New commands: upgrade and downgrade
The "upgrade" command converts current database to the numsync
(extended) format. The "downgrade" command converts current database
to the standard format.
** New command: snapshot
The "snapshot" command is part of the new crash tolerance support.
Given the names of two snapshot files, it analyzes them and selects
the one to be used for database recovery. See the GDBM manual,
section 17.5 "Manual crash recovery" for a detailed discussion of its
use.
|
|
|
|
|
|
|
|
Upstream changes: bug fixes
|
|
|
|
|
|
This library was merged into the libldap and removed in the recent release.
|
|
2.12.1 (2021-08-26)
* Support Ruby 3.0.
* Move to GitHub actions.
|
|
This takes advantage of the introduction of the SYSCONFBASE variable.
Tested on NetBSD/amd64 and macOS/amd64.
ok adam@
Bumps PKGREVISION.
|
|
Readme.md say to pull the pgx crates from the "timescale" branch, but the
Cargo.toml specifies the "guardless" branch ...
|
|
The update was incomplete because I forgot to update the GITHUB_TAG.
|
|
|
