![[BACK]](/icons/back.gif){kind=icon}
Up to [cvs.NetBSD.org] / pkgsrc / databases / postgresql10-client
Request diff between arbitrary revisions
Default branch: MAIN
Revision 1.32, Mon Mar 6 08:27:00 2023 UTC (13 months, 2 weeks ago) by adam
Branch: MAIN
CVS Tags: HEAD
Changes since 1.31: +1 -1
lines
FILE REMOVED
postgresql10: removed; end of life
Revision 1.31 / (download) - annotate - [select for diffs], Wed Nov 23 16:19:37 2022 UTC (16 months, 3 weeks ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2022Q4-base,
pkgsrc-2022Q4
Changes since 1.30: +2 -1
lines
Diff to previous 1.30 (colored) to selected 1.22 (colored)
massive revision bump after textproc/icu update
Revision 1.30 / (download) - annotate - [select for diffs], Sun Nov 13 09:34:24 2022 UTC (17 months ago) by adam
Branch: MAIN
Changes since 1.29: +1 -2
lines
Diff to previous 1.29 (colored) to selected 1.22 (colored)
postgresql1[0-5]: Updated to 15.1, 14.6, 13.9, 12.13, 11.18, and 10.23 PostgreSQL 15.1, 14.6, 13.9, 12.13, 11.18, and 10.23 Released! Bug Fixes and Improvements This update fixes over 25 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 15. Some of these issues may also affect other supported versions of PostgreSQL. Included in this release: Fix for updatable views for INSERT statements that include multi-row VALUES clauses with a DEFAULT set. Disallow rules named _RETURN that are not ON SELECT rules. Disallow use of MERGE on a partitioned table that has foreign-table partitions. Fix for construction of per-partition foreign key constraints while doing ALTER TABLE ... ATTACH PARTITION, where previously incorrect or duplicate constraints could be built. Fix for a planner failure with extended statistics on partitioned or inherited tables. Fix bugs in logical decoding that could lead to memory leaks when replay starts from a point between the beginning of a transaction and the beginning of its subtransaction. Fix issues with slow shutdown of replication workers by allowing interrupts in more places. Disallow logical replication into foreign-table partitions. Prevent crash in replication works after a SQL or PL/pgSQL function syntax error. psql -c now exits with a nonzero status if the query is canceled. Allow cross-platform tablespace relocation in pg_basebackup. Fix pg_dump to include comments attached to some CHECK constraints.
Revision 1.29 / (download) - annotate - [select for diffs], Sun Oct 16 14:42:49 2022 UTC (18 months ago) by gdt
Branch: MAIN
Changes since 1.28: +2 -1
lines
Diff to previous 1.28 (colored) to selected 1.22 (colored)
databases/postgresql*: Work around autoconf mkdir bug autoconf does not accept NetBSD mkdir (this bug has already been fixed in upstream autoconf). This leads to install.sh, and thus postgresql's workaround for a relative path in pgxs, and then that being used in postgis. Somewhere in that chain there is a bug leading to postgis failing to make a directory at install time. This passes in an autoconf cache variable so that for mkdir it uses mkdir (which it does on GNU/Linux, and thus that situation is well-tested).
Revision 1.28 / (download) - annotate - [select for diffs], Mon Aug 15 20:59:35 2022 UTC (20 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2022Q3-base,
pkgsrc-2022Q3
Changes since 1.27: +1 -2
lines
Diff to previous 1.27 (colored) to selected 1.22 (colored)
postgresql: updated to 14.5, 13.8, 12.12, 11.17, 10.22 This update fixes over 40 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 14. Some of these issues may also affect other supported versions of PostgreSQL. Included in this release: Fix replay of CREATE DATABASE write-ahead log (WAL) records on standby servers when encountering a missing tablespace directory. Add support for tablespaces that are plain directories instead of symbolic links to other directories. Fix permission checks in CREATE INDEX to use the user's permissions. This fixes broken dump/restore scenarios that relied on the behavior prior to the fix for CVE-2022-1552. In the extended query protocol, force an immediate commit after CREATE DATABASE and other commands that can't run in a transaction block. Fix a race condition around checking transaction visibility that was more likely to happen when using synchronous replication. Fix incorrect permission-checking code for extended statistics. Fix extended statistics machinery to handle most common value (MCV)-type statistics on boolean-valued expressions. Avoid planner core dump with constant = ANY(array) clauses when there are MCV-type extended statistics on the array variable. Allow cancellation of ANALYZE while it is computing extended statistics. Fix ALTER TABLE ... ENABLE/DISABLE TRIGGER to handle recursion for triggers on partitioned tables. Reject ROW() expressions and functions in FROM that have more than 1600 columns. Fix memory leak in logical replication subscribers. Fix checks in logical replication of replica identity when the target table is partitioned. Arrange to clean up after commit-time errors within SPI_commit(), rather than expecting callers to do that. This includes a fix for the same scenario in PL/Python, which had reported crashes on Python 3.11 and memory leaks on older versions of Python 3. Improve handling in libpq of idle states in pipeline mode. In the psql \watch command, echo a newline after cancellation with control-C. Fix pg_upgrade to detect non-upgradable usages of functions accepting anyarray parameters. Several postgres_fdw fixes, including prevention of batch insertions when there are WITH CHECK OPTION constraints present.
Revision 1.27 / (download) - annotate - [select for diffs], Mon Jul 18 22:13:20 2022 UTC (21 months ago) by tnn
Branch: MAIN
Changes since 1.26: +2 -2
lines
Diff to previous 1.26 (colored) to selected 1.22 (colored)
postgresql*-client: fix installed PGXS Makefiles when using pkgsrc gettext
If we are using the "nls" PKG_OPTION together with pkgsrc gettext, then
we must ensure CPPFLAGS contains -I${PREFIX}/include/gettext.
The installed postgresql/server/c.h expects to be able to include
<libintl.h> using the CPPFLAGS that get installed in Makefile.global.
Without this it is not possible to develop PGXS extensions
outside of pkgsrc.
Revision 1.26 / (download) - annotate - [select for diffs], Tue Jun 28 11:31:32 2022 UTC (21 months, 3 weeks ago) by wiz
Branch: MAIN
Changes since 1.25: +2 -1
lines
Diff to previous 1.25 (colored) to selected 1.22 (colored)
*: recursive bump for perl 5.36
Revision 1.25 / (download) - annotate - [select for diffs], Thu May 12 19:02:42 2022 UTC (23 months, 1 week ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2022Q2-base,
pkgsrc-2022Q2
Changes since 1.24: +1 -2
lines
Diff to previous 1.24 (colored) to selected 1.22 (colored)
postgresqlNN: updated to 14.3, 13.7, 12.11, 11.16, and 10.21 The PostgreSQL Global Development Group has released an update to all supported versions of PostgreSQL, including 14.3, 13.7, 12.11, 11.16, and 10.21. This release closes one security vulnerability and fixes over 50 bugs reported over the last three months. CVE-2022-1552: Autovacuum, REINDEX, and others omit "security restricted operation" sandbox. Versions Affected: 10 - 14. The security team typically does not test unsupported versions, but this problem is quite old. Autovacuum, REINDEX, CREATE INDEX, REFRESH MATERIALIZED VIEW, CLUSTER, and pg_amcheck made incomplete efforts to operate safely when a privileged user is maintaining another user's objects. Those commands activated relevant protections too late or not at all. An attacker having permission to create non-temp objects in at least one schema could execute arbitrary SQL functions under a superuser identity. While promptly updating PostgreSQL is the best remediation for most users, a user unable to do that can work around the vulnerability by disabling autovacuum, not manually running the above commands, and not restoring from output of the pg_dump command. Performance may degrade quickly under this workaround. VACUUM is safe, and all commands are fine when a trusted user owns the target object. Bug Fixes and Improvements This update fixes over 50 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 14. Some of these issues may also affect other supported versions of PostgreSQL. Included in this release: Fix issue that could lead to corruption of GiST indexes on ltree columns. After upgrading, you will need to reindex any GiST indexes on ltree columns. Column names in tuples produced by a whole-row variable (e.g. tbl.*) outside of a top-level of a SELECT list are now always associated with those of the associated named composite type, if there is one. The release notes detail a workaround if you depend on the previous behavior. Fix incorrect rounding when extracting epoch values from interval types. Prevent issues with calling pg_stat_get_replication_slot(NULL). Fix incorrect output for types timestamptz and timetz in table_to_xmlschema(). Fix errors related to a planner issue that affected asynchronous remote queries. Fix planner failure if a query using SEARCH or CYCLE features contains a duplicate common-table expression (WITH) name. Fix ALTER FUNCTION to support changing a function's parallelism property and its SET-variable list in the same command. Fix incorrect sorting of table rows when using CLUSTER on an index whose leading key is an expression. Prevent data loss if a system crash occurs shortly after a sorted GiST index build. Fix risk of deadlock failures while dropping a partitioned index. Fix race condition between DROP TABLESPACE and checkpointing that could fail to remove all dead files from the tablespace directory. Fix potential issue in crash recovery after a TRUNCATE command that overlaps with a checkpoint. Re-allow _ as the first character in a custom configuration parameter name. Fix PANIC: xlog flush request is not satisfied failure during standby promotion when there is a missing WAL continuation record. Fix possibility of self-deadlock in hot standby conflict handling. Ensure that logical replication apply workers can be restarted when the server is near the max_sync_workers_per_subscription limit. Disallow execution of SPI functions during PL/Perl function compilation. libpq now accepts root-owned SSL private key files, which matches the rules the server has used since the 9.6 release. Re-allow database.schema.table patterns in psql, pg_dump, and pg_amcheck. Several fixes for pageinspect to improve overall stability. Disable batch insertion in postgres_fdw when BEFORE INSERT ... FOR EACH ROW triggers exist on the foreign table. Update JIT code to work with LLVM 14.
Revision 1.24 / (download) - annotate - [select for diffs], Thu May 5 08:22:37 2022 UTC (23 months, 2 weeks ago) by nia
Branch: MAIN
Changes since 1.23: +2 -2
lines
Diff to previous 1.23 (colored) to selected 1.22 (colored)
postgresql*-client: Use OPSYS_VERSION to numerically compare NetBSD versions XXX do we still want to keep hacks for NetBSD 3?
Revision 1.23 / (download) - annotate - [select for diffs], Mon Apr 18 19:10:39 2022 UTC (2 years ago) by adam
Branch: MAIN
Changes since 1.22: +2 -1
lines
Diff to previous 1.22 (colored)
revbump for textproc/icu update
Revision 1.22 / (download) - annotate - [selected], Fri Feb 11 08:31:20 2022 UTC (2 years, 2 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2022Q1-base,
pkgsrc-2022Q1
Changes since 1.21: +1 -2
lines
Diff to previous 1.21 (colored)
postgresql1N: updated to 14.2, 13.6, 12.10, 11.15, and 10.20 PostgreSQL 14.2, 13.6, 12.10, 11.15, and 10.20 Released! This update fixes over 55 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 14. Some of these issues may also affect other supported versions of PostgreSQL. Included in this release: Fix for a low probability scenario of index corruption when a HOT (heap-only tuple) chain changes state during VACUUM. Encountering this issue is unlikely, but if you are concerned, please consider reindexing. Fix for using REINDEX CONCURRENTLY on TOAST table indexes to prevent corruption. You can fix any TOAST indexes by reindexing them again. The psql \password command now defaults to setting the password for the role defined by CURRENT_USER. Additionally, the role name is now included in the password prompt. Build extended statistics for partitioned tables. If you previously added extended statistics to a partitioned table, you should run ANALYZE on those tables. As autovacuum currently does not process partitioned tables, you must periodically run ANALYZE on any partitioned tables to update their statistics. Fix crash with ALTER STATISTICS when the statistics object is dropped concurrently. Fix crash with multiranges when extracting variable-length data types. Several fixes to the query planner that lead to incorrect query results. Several fixes for query plan memoization. Fix startup of a physical replica to tolerate transaction ID wraparound. When using logical replication, avoid duplicate transmission of a partitioned table's data when the publication includes both the child and parent tables. Disallow altering data type of a partitioned table's columns when the partitioned table's row type is used as a composite type elsewhere. Disallow ALTER TABLE ... DROP NOT NULL for a column that is part of a replica identity index. Several fixes for caching that correct logical replication behavior and improve performance. Fix memory leak when updating expression indexes. Avoid leaking memory during REASSIGN OWNED BY operations that reassign ownership of many objects. Fix display of whole-row variables appearing in INSERT ... VALUES rules. Fix race condition that could lead to failure to localize error messages that are reported early in multi-threaded use of libpq or ecpglib. Fix psql \d command for identifying parent triggers. Fix failures on Windows when using the terminal as data source or destination. This affected the psql \copy command and using pg_recvlogical with -f -. Fix the pg_dump --inserts and --column-inserts modes to handle tables that contain both generated and dropped columns. Fix edge cases in how postgres_fdw handles asynchronous queries. These errors could lead to crashes or incorrect results when attempting to run parallel scans of foreign tables. For the full list of changes available, please review the release notes.
Revision 1.21 / (download) - annotate - [select for diffs], Wed Dec 8 16:03:42 2021 UTC (2 years, 4 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2021Q4-base,
pkgsrc-2021Q4
Changes since 1.20: +2 -1
lines
Diff to previous 1.20 (colored) to selected 1.22 (colored)
revbump for icu and libffi
Revision 1.20 / (download) - annotate - [select for diffs], Fri Aug 13 11:54:43 2021 UTC (2 years, 8 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2021Q3-base,
pkgsrc-2021Q3
Changes since 1.19: +1 -2
lines
Diff to previous 1.19 (colored) to selected 1.22 (colored)
postgresql: updated to 13.4, 12.8, 11.13, 10.18, 9.6.23 PostgreSQL 13.4, 12.8, 11.13, 10.18, 9.6.23 Security Issues CVE-2021-3677: Memory disclosure in certain queries Versions Affected: 11 - 13. A purpose-crafted query can read arbitrary bytes of server memory. In the default configuration, any authenticated database user can complete this attack at will. The attack does not require the ability to create objects. If server settings include max_worker_processes=0, the known versions of this attack are infeasible. However, undiscovered variants of the attack may be independent of that setting. Bug Fixes and Improvements This update also fixes over 75 bugs that were reported in the last several months. Some of these issues affect only version 13, but many affect all supported versions. Some of these fixes include: Completely disable TLS/SSL renegotiation. This was previously disabled, but the server would still execute a client-initiated renegotiation request. Restore the Portal-level snapshot after COMMIT or ROLLBACK within a procedure. This change fixes cases where an attempt to fetch a toasted value immediately after COMMIT/ROLLBACK would fail with errors like "no known snapshots" or "missing chunk number 0 for toast value". Avoid misbehavior when persisting the output of a cursor that's reading a volatile query. Reject cases where a query in WITH rewrites to just NOTIFY, which would cause a crash. Several corner-case fixes for numeric types. ALTER EXTENSION now locks the extension when adding or removing a member object. The "enabled" status is now copied when a partitioned table's triggers are cloned to a new partition. Avoid alias conflicts in queries generated for REFRESH MATERIALIZED VIEW CONCURRENTLY. This command failed on materialized views containing columns with certain names, notably mv and newdata. Disallow whole-row variables in GENERATED expressions. Several fixes for DROP OWNED BY behavior in relation to row-level security (RLS) policies. Re-allow old-style Windows locale names in CREATE COLLATION commands. walsenders now show their latest replication command in pg_stat_activity, instead of just showing the latest SQL command. pg_settings.pending_restart now shows as true when a pertinent entry in postgresql.conf is removed. On 64-bit Windows, allow the effective value of work_mem * hash_mem_multiplier to exceed 2GB. Update minimum recovery point when WAL replay of a transaction abort record causes file truncation. Advance oldest-required-WAL-segment horizon properly after a replication slot is invalidated. This fixes an issue where the server's WAL storage could run out of space. Improve progress reporting for the sort phase of a parallel B-tree index build. Fix assorted crash cases in logical replication of partitioned-table updates and when firing AFTER triggers of partitioned tables. Prevent infinite loops in SP-GiST index insertion. Ensure that SP-GiST index insertion can be terminated by a query cancel request. In psql and other client programs, avoid overrunning the ends of strings when dealing with invalidly-encoded data. Fix pg_dump to correctly handle triggers on partitioned tables whose enabled status is different from their parent triggers' status. Avoid "invalid creation date in header" warnings when running pg_restore on a file created in a different time zone. pg_upgrade now carries forward the old installation's oldestXID value and no longer forces an anti-wraparound VACUUM." Extend pg_upgrade to detect and warn about extensions that should be upgraded. Fix contrib/postgres_fdw to better work with generated columns, so long as a generated column in a foreign table represents a generated column in the remote table.
Revision 1.19 / (download) - annotate - [select for diffs], Mon May 24 19:49:45 2021 UTC (2 years, 10 months ago) by wiz
Branch: MAIN
CVS Tags: pkgsrc-2021Q2-base,
pkgsrc-2021Q2
Changes since 1.18: +2 -1
lines
Diff to previous 1.18 (colored) to selected 1.22 (colored)
*: recursive bump for perl 5.34
Revision 1.18 / (download) - annotate - [select for diffs], Tue May 18 11:56:17 2021 UTC (2 years, 11 months ago) by adam
Branch: MAIN
Changes since 1.17: +1 -2
lines
Diff to previous 1.17 (colored) to selected 1.22 (colored)
postgresql: updated to 13.3, 12.7, 11.12, 10.17, 9.6.22
PostgreSQL 13.3, 12.7, 11.12, 10.17, and 9.6.22 Released!
Posted on 2021-05-13 by PostgreSQL Global Development Group
PostgreSQL Project Security
The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 13.3, 12.7, 11.12, 10.17, and 9.6.22. This release closes three security vulnerabilities and fixes over 45 bugs reported over the last three months.
For the full list of changes, please review the release notes.
Security Issues
CVE-2021-32027: Buffer overrun from integer overflow in array subscripting calculations
Versions Affected: 9.6 - 13. The security team typically does not test unsupported versions, but this problem is quite old.
While modifying certain SQL array values, missing bounds checks let authenticated database users write arbitrary bytes to a wide area of server memory.
The PostgreSQL project thanks Tom Lane for reporting this problem.
CVE-2021-32028: Memory disclosure in INSERT ... ON CONFLICT ... DO UPDATE
Versions Affected: 9.6 - 13. The security team typically does not test unsupported versions. The feature first appeared in 9.5.
Using an INSERT ... ON CONFLICT ... DO UPDATE command on a purpose-crafted table, an attacker can read arbitrary bytes of server memory. In the default configuration, any authenticated database user can create prerequisite objects and complete this attack at will. A user lacking the CREATE and TEMPORARY privileges on all databases and the CREATE privilege on all schemas cannot use this attack at will.
The PostgreSQL project thanks Andres Freund for reporting this problem.
CVE-2021-32029: Memory disclosure in partitioned-table UPDATE ... RETURNING
Versions Affected: 11 - 13
Using an UPDATE ... RETURNING on a purpose-crafted partitioned table, an attacker can read arbitrary bytes of server memory. In the default configuration, any authenticated database user can create prerequisite objects and complete this attack at will. A user lacking the CREATE and TEMPORARY privileges on all databases and the CREATE privilege on all schemas typically cannot use this attack at will.
The PostgreSQL project thanks Tom Lane for reporting this problem.
Bug Fixes and Improvements
This update fixes over 45 bugs that were reported in the last several months. Some of these issues only affect version 13, but could also apply to other supported versions.
Some of these fixes include:
Fix potential incorrect computation of UPDATE ... RETURNING outputs for joined, cross-partition updates.
Fix ALTER TABLE ... ALTER CONSTRAINT when used on foreign-key constraints on partitioned tables. The command would fail to adjust the DEFERRABLE and/or INITIALLY DEFERRED properties of the constraints and triggers of leaf partitions, leading to unexpected behavior. After updating to this version, you can execute the ALTER TABLE ... ALTER CONSTRAINT command to fix any misbehaving partitioned tables.
Ensure that when a child table is attached with ALTER TABLE ... INHERIT that generated columns in the parent are generated in the same way in the child.
Forbid marking an identity column as NULL.
Allow ALTER ROLE ... SET/ALTER DATABASE ... SET to set the role, session_authorization, and temp_buffers parameters.
Ensure that REINDEX CONCURRENTLY preserves any statistics target set for the index.
Fix an issue where, in some cases, saving records within AFTER triggers could cause crashes.
Fix how to_char() handles Roman-numeral month format codes with negative intervals.
Fix use of uninitialized value while parsing an \{m,n\} quantifier in a BRE-mode regular expression.
Fix "could not find pathkey item to sort" planner errors that occur in some situations when the sort key involves an aggregate or window function.
Fix issue with BRIN index bitmap scans that could lead to "could not open file" errors.
Fix potentially wrong answers from GIN tsvector index searches when there are many matching records.
Fixes for COMMIT AND CHAIN functionality on both the server and psql.
Avoid incorrect timeline change while recovering uncommitted two-phase transactions from WAL, which could lead to consistency issues and the inability to restart the server.
Ensure thatwal_sync_method is set to fdatasync by default on newer FreeBSD releases.
Disable the vacuum_cleanup_index_scale_factor parameter and storage option.
Fix several memory leaks in the server, including one with SSL/TLS parameter initialization.
Restore the previous behavior of \connect service=XYZ to psql, i.e. disallow environmental variables (e.g. PGPORT) from overriding entries in the service file.
Fix how pg_dump handles generated columns in partitioned tables.
Add additional checks to pg_upgrade for user tables containing non-upgradable data types.
On Windows, initdb now prints instructions about how to start the server with pg_ctl using backslash separators.
Fix pg_waldump to count XACT records correctly when generating per-record statistics.
Revision 1.17 / (download) - annotate - [select for diffs], Wed Apr 21 11:41:14 2021 UTC (2 years, 11 months ago) by adam
Branch: MAIN
Changes since 1.16: +2 -1
lines
Diff to previous 1.16 (colored) to selected 1.22 (colored)
revbump for textproc/icu
Revision 1.16 / (download) - annotate - [select for diffs], Fri Feb 19 13:47:03 2021 UTC (3 years, 1 month ago) by joerg
Branch: MAIN
CVS Tags: pkgsrc-2021Q1-base,
pkgsrc-2021Q1
Changes since 1.15: +3 -2
lines
Diff to previous 1.15 (colored) to selected 1.22 (colored)
Build fe_utils first for all Postgres versions that have it.
Revision 1.15 / (download) - annotate - [select for diffs], Mon Feb 15 18:58:36 2021 UTC (3 years, 2 months ago) by adam
Branch: MAIN
Changes since 1.14: +1 -2
lines
Diff to previous 1.14 (colored) to selected 1.22 (colored)
postgresql: updated to 13.2, 12.6, 11.11, 10.16, 9.6.21, and 9.5.25 The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 13.2, 12.6, 11.11, 10.16, 9.6.21, and 9.5.25. This release closes two security vulnerabilities and fixes over 80 bugs reported over the last three months. Additionally, this is the final release of PostgreSQL 9.5. If you are running PostgreSQL 9.5 in a production environment, we suggest that you make plans to upgrade. For the full list of changes, please review the release notes. Security Issues CVE-2021-3393: Partition constraint violation errors leak values of denied columns Versions Affected: 11 - 13. A user having an UPDATE privilege on a partitioned table but lacking the SELECT privilege on some column may be able to acquire denied-column values from an error message. This is similar to CVE-2014-8161, but the conditions to exploit are more rare. The PostgreSQL project thanks Heikki Linnakangas for reporting this problem. CVE-2021-20229: Single-column SELECT privilege enables reading all columns Versions Affected: 13. A user having a SELECT privilege on an individual column can craft a special query that returns all columns of the table. Additionally, a stored view that uses column-level privileges will have incomplete column-usage bitmaps. In installations that depend on column-level permissions for security, it is recommended to execute CREATE OR REPLACE on all user-defined views to force them to be re-parsed. The PostgreSQL project thanks Sven Klemm for reporting this problem. Bug Fixes and Improvements This update fixes over 80 bugs that were reported in the last several months. Some of these issues only affect version 13, but could also apply to other supported versions. Some of these fixes include: Fix an issue with GiST indexes where concurrent insertions could lead to a corrupt index with entries placed in the wrong pages. You should REINDEX any affected GiST indexes. Fix CREATE INDEX CONCURRENTLY to ensure rows from concurrent prepared transactions are included in the index. Installations that have enabled prepared transactions should REINDEX any concurrently-built indexes. Fix for possible incorrect query results when a hash aggregation is spilled to disk. Fix edge case in incremental sort that could lead to sorting results incorrectly or a "retrieved too many tuples in a bounded sort" error. Avoid crash when a CALL or DO statement that performs a transaction rollback is executed via extended query protocol, such as from prepared statements. Fix a failure when a PL/pgSQL procedure used CALL on another procedure that has OUT parameters that executed a COMMIT or ROLLBACK. Remove errors from BEFORE UPDATE triggers on partitioned tables for restrictions that no longer apply. Several fixes for queries with joins that could lead to error messages such as "no relation entry for relid N" or "failed to build any N-way joins". Do not consider parallel-restricted or set-returning functions in an ORDER BY expressions when trying to parallelize sorts. Fix ALTER DEFAULT PRIVILEGES to handle duplicate arguments safely. Several fixes in behavior when wal_level is set to minimal, including when tables are rewritten within a transaction. Several fixes for CREATE TABLE LIKE. Ensure that allocated disk space for a dropped relation (e.g. a table) is released promptly when a transaction is committed. Fix progress reporting for CLUSTER. Fix handling of backslash-escaped multibyte characters in COPY FROM. Fix recently-introduced race conditions in LISTEN/NOTIFY queue handling. Allow the jsonb concatenation operator (||) to handle all combinations of JSON data types. Fix WAL-reading logic so that standbys can handle timeline switches correctly. This issue could have shown itself with errors like "requested WAL segment has already been removed". Several leak fixes for the walsender process around logical decoding and replication. Ensure that a nonempty value of krb_server_keyfile always overrides any setting of KRB5_KTNAME in the server environment Several fixes for GSS encryption support. Ensure the \connect command allows the use of a password in the connection_string argument. Fix assorted bugs with the \help command. Several fixes for pg_dump. Ensure that pg_rewind accounts for all WAL when rewinding a standby server. Fix memory leak in contrib/auto_explain. Ensure all postgres_fdw connections are closed if the a user mapping or foreign server object those connections depend on are dropped. Fix JIT compilation to be compatible with LLVM 11 and LLVM 12. This update also contains tzdata release 2021a for DST law changes in Russia (Volgograd zone) and South Sudan, plus historical corrections for Australia, Bahamas, Belize, Bermuda, Ghana, Israel, Kenya, Nigeria, Palestine, Seychelles, and Vanuatu. Notably, the Australia/Currie zone has been corrected to the point where it is identical to Australia/Hobart. For the full list of changes available, please review the release notes. PostgreSQL 9.5 is EOL This is the final release of PostgreSQL 9.5. If you are running PostgreSQL 9.5 in a production environment, we suggest that you make plans to upgrade to a newer, supported version of PostgreSQL. Please see our versioning policy for more information.
Revision 1.14 / (download) - annotate - [select for diffs], Fri Dec 4 04:55:42 2020 UTC (3 years, 4 months ago) by riastradh
Branch: MAIN
CVS Tags: pkgsrc-2020Q4-base,
pkgsrc-2020Q4
Changes since 1.13: +2 -1
lines
Diff to previous 1.13 (colored) to selected 1.22 (colored)
Revbump for openpam cppflags change months ago, belatedly.
Revision 1.13 / (download) - annotate - [select for diffs], Mon Nov 16 12:15:02 2020 UTC (3 years, 5 months ago) by adam
Branch: MAIN
Changes since 1.12: +2 -3
lines
Diff to previous 1.12 (colored) to selected 1.22 (colored)
postgresql: updated to 13.1, 12.5, 11.10, 10.15, 9.6.20, and 9.5.24 PostgreSQL 13.1, 12.5, 11.10, 10.15, 9.6.20, and 9.5.24 Security Issues * CVE-2020-25695: Multiple features escape "security restricted operation" sandbox * CVE-2020-25694: Reconnection can downgrade connection security settings * CVE-2020-25696: psql's \gset allows overwriting specially treated variables Bug Fixes and Improvements This update also fixes over 65 bugs that were reported in the last several months. Some of these issues only affect version 13, but may also apply to other supported versions. Some of these fixes include: Fix a breakage in the replication protocol by ensuring that two "command completion" events are expected for START_REPLICATION. Ensure fsync is called on the SLRU caches that PostgreSQL maintains. This prevents potential data loss due to an operating system crash. Fix ALTER ROLE usage for users with the BYPASSRLS permission. ALTER TABLE ONLY ... DROP EXPRESSION is disallowed on partitioned tables when there are child tables. Ensure that ALTER TABLE ONLY ... ENABLE/DISABLE TRIGGER does not apply to child tables. Fix for ALTER TABLE ... SET NOT NULL on partitioned tables to avoid a potential deadlock in parallel pg_restore. Fix handling of expressions in CREATE TABLE LIKE with inheritance. DROP INDEX CONCURRENTLY is disallowed on partitioned tables. Allow LOCK TABLE to succeed on a self-referential view instead of throwing an error. Several fixes around statistics collection and progress reporting for REINDEX CONCURRENTLY. Ensure that GENERATED columns are updated when any columns they depend on are updated via a rule or an updatable view. Support hash partitioning with text array columns as partition keys. Allow the jsonpath .datetime() method to accept ISO 8601-format timestamps. During a "smart" shutdown, ensure background processes are not terminated until all foreground client sessions are completed, fixing an issue that broke the processing of parallel queries. Several fixes for the query planner and optimizer. Ensure that data is de-toasted before being inserted into a BRIN index. This could manifest itself with errors like "missing chunk number 0 for toast value NNN". If you have seen a similar error in an existing BRIN index, you should be able to correct it by using REINDEX on the index. Fix the output of EXPLAIN to have the correct XML tag nesting for incremental sort plans. Several fixes for memory leaks, including ones involving RLS policies, using CALL with PL/pgSQL, SIGHUP processing a configuration parameter that cannot be applied without a restart, and an edge-case for index lookup for a partition. libpq can now support arbitrary-length lines in the .pgpass file. On Windows, psql now reads the output of a backtick command in text mode, not binary mode, so it can now properly handle newlines. Fix how pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb use complex connection-string parameters. When the \connect command of psql reuses connection parameters, ensure that all non-overridden parameters from a previous connection string are also re-used. Ensure that pg_dump collects per-column information about extension configuration tables, avoiding crashes when specifying --inserts. Ensure that parallel pg_restore processes foreign keys referencing partitioned tables in the correct order. Several fixes for contrib/pgcrypto, including a memory leak fix.
Revision 1.12 / (download) - annotate - [select for diffs], Thu Nov 5 09:07:43 2020 UTC (3 years, 5 months ago) by ryoon
Branch: MAIN
Changes since 1.11: +2 -2
lines
Diff to previous 1.11 (colored) to selected 1.22 (colored)
*: Recursive revbump from textproc/icu-68.1
Revision 1.11 / (download) - annotate - [select for diffs], Mon Aug 31 18:07:09 2020 UTC (3 years, 7 months ago) by wiz
Branch: MAIN
CVS Tags: pkgsrc-2020Q3-base,
pkgsrc-2020Q3
Changes since 1.10: +2 -1
lines
Diff to previous 1.10 (colored) to selected 1.22 (colored)
*: bump PKGREVISION for perl-5.32.
Revision 1.10 / (download) - annotate - [select for diffs], Fri Aug 14 06:56:22 2020 UTC (3 years, 8 months ago) by adam
Branch: MAIN
Changes since 1.9: +1 -2
lines
Diff to previous 1.9 (colored) to selected 1.22 (colored)
postgresql: updated to 12.4, 11.9, 10.14, 9.6.19, 9.5.23 PostgreSQL 12.4, 11.9, 10.14, 9.6.19, 9.5.23 Security Issues CVE-2020-14349: Uncontrolled search path element in logical replication. Versions Affected: 10 - 12. The PostgreSQL search_path setting determines schemas searched for tables, functions, operators, etc. The CVE-2018-1058 fix caused most PostgreSQL-provided client applications to sanitize search_path, but logical replication continued to leave search_path unchanged. Users of a replication publisher or subscriber database can create objects in the public schema and harness them to execute arbitrary SQL functions under the identity running replication, often a superuser. Installations having adopted a documented secure schema usage pattern are not vulnerable. The PostgreSQL project thanks Noah Misch for reporting this problem. CVE-2020-14350: Uncontrolled search path element in CREATE EXTENSION. Versions Affected: 9.5 - 12. The security team typically does not test unsupported versions, but this problem is quite old. When a superuser runs certain CREATE EXTENSION statements, users may be able to execute arbitrary SQL functions under the identity of that superuser. The attacker must have permission to create objects in the new extension's schema or a schema of a prerequisite extension. Not all extensions are vulnerable. In addition to correcting the extensions provided with PostgreSQL, the PostgreSQL Global Development Group is issuing guidance for third-party extension authors to secure their own work. Bug Fixes and Improvements This update also fixes over 50 bugs that were reported in the last several months. Some of these issues affect only version 12, but many affect all supported versions. Some of these fixes include: Fix edge cases in partition pruning involving multiple partition key columns with multiple or no constraining WHERE clauses. Several fixes for query planning and execution involving partitions. Fix for determining when to execute a column-specific UPDATE trigger on a logical replication subscriber. pg_replication_slot_advance() now updates the oldest xmin and LSN values, as the failure to do this could prevent resources (e.g. WAL files) from being cleaned up. Fix a performance regression in ts_headline(). Ensure that pg_read_file() and related functions read until EOF is reached, which fixes compatibility with pipes and other virtual files. Forbid numeric NaN values in jsonpath computations, which do not exist in SQL nor JSON. Several fixes for NaN inputs with aggregate functions. This fixes a change in PostgreSQL 12 where NaN values caused the following aggregates to emit values of 0 instead of NaN: corr(), covar_pop(), regr_intercept(), regr_r2(), regr_slope(), regr_sxx(), regr_sxy(), regr_syy(), stddev_pop(), and var_pop(). time and timetz values fractionally greater than 24:00:00 are now rejected. Several fixes for EXPLAIN, including a fix for reporting resource usage when a plan uses parallel workers with "Gather Merge" nodes. Fix timing of constraint revalidation in ALTER TABLE that could lead to odd errors. Fix for REINDEX CONCURRENTLY that could prevent old values from being included in future logical decoding output. Fix for LATERAL references that could potentially cause crashes during query execution. Use the collation specified for a query when estimating operator costs Fix conflict-checking anomalies in SERIALIZABLE transaction isolation mode. Ensure checkpointer process discards file sync requests when fsync is off Fix issue where pg_control could be written out with an inconsistent checksum, which could lead to the inability to restart the database if it crashed before the next pg_control update. Ensure that libpq continues to try to read from the database connection socket after a write failure, as this allows the connection to collect any final error messages from the server. Report out-of-disk-space errors properly in pg_dump and pg_basebackup Several fixes for pg_restore, including a fix for parallel restore on tables that have both table-level and column-level privileges. Fix for pg_upgrade to ensure it runs with vacuum_defer_cleanup_age set to 0. Fix how pg_rewind handles just-deleted files in the source data directory Fix failure to initialize local state correctly in contrib/dblink, which could lead to dblink_close() issuing an unexpected COMMIT on the remote server. Change contrib/amcheck to not report about deleted index pages that are empty, as this is normal during WAL replay.
Revision 1.9 / (download) - annotate - [select for diffs], Tue Jun 2 08:23:27 2020 UTC (3 years, 10 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2020Q2-base,
pkgsrc-2020Q2
Changes since 1.8: +2 -1
lines
Diff to previous 1.8 (colored) to selected 1.22 (colored)
Revbump for icu
Revision 1.8 / (download) - annotate - [select for diffs], Wed May 13 04:58:21 2020 UTC (3 years, 11 months ago) by rillig
Branch: MAIN
Changes since 1.7: +2 -1
lines
Diff to previous 1.7 (colored) to selected 1.22 (colored)
databases/postgresql: suppress USE_TOOLS+=perl warning
Revision 1.7 / (download) - annotate - [select for diffs], Fri Feb 14 17:06:40 2020 UTC (4 years, 2 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2020Q1-base,
pkgsrc-2020Q1
Changes since 1.6: +2 -3
lines
Diff to previous 1.6 (colored) to selected 1.22 (colored)
postgresqlNN: updated to 12.2, 11.7, 10.12, 9.6.17, 9.5.21, and 9.4.26 PostgreSQL 12.2, 11.7, 10.12, 9.6.17, 9.5.21, and 9.4.26 PostgreSQL 9.4 Now EOL This is the last release for PostgreSQL 9.4, which will no longer receive security updates and bug fixes. PostgreSQL 9.4 introduced new features such as JSONB support, the ALTER SYSTEM command, the ability to stream logical changes to an output plugin, and more. While we are very proud of this release, these features are also found in newer versions of PostgreSQL. Many of these features have also received improvements, and, per our versioning policy, it is time to retire PostgreSQL 9.4. To receive continued support, we suggest that you make plans to upgrade to a newer, supported version of PostgreSQL. Please see the PostgreSQL versioning policy for more information. Security Issues CVE-2020-1720: ALTER ... DEPENDS ON EXTENSION is missing authorization checks. Versions Affected: 9.6 - 12 The ALTER ... DEPENDS ON EXTENSION sub-commands do not perform authorization checks, which can allow an unprivileged user to drop any function, procedure, materialized view, index, or trigger under certain conditions. This attack is possible if an administrator has installed an extension and an unprivileged user can CREATE, or an extension owner either executes DROP EXTENSION predictably or can be convinced to execute DROP EXTENSION. Bug Fixes and Improvements This update also fixes over 75 bugs that were reported in the last several months. Some of these issues affect only version 12, but may also affect all supported versions. Some of these fixes include: Fix for partitioned tables with foreign-key references where TRUNCATE ... CASCADE would not remove all data. If you have previously used TRUNCATE ... CASCADE on a partitioned table with foreign-key references please see the "Updating" section for verification and cleanup steps. Fix failure to add foreign key constraints to table with sub-partitions (aka a multi-level partitioned table). If you have previously used this functionality, you can fix it by either detaching and re-attaching the affected partition, or by dropping and re-adding the foreign key constraint to the parent table. You can find more information on how to perform these steps in the ALTER TABLE documentation. Fix performance issue for partitioned tables introduced by the fix for CVE-2017-7484 that now allows the planner to use statistics on a child table for a column that the user is granted access to on the parent table when the query contains a leaky operator. Several other fixes and changes for partitioned tables, including disallowing partition key expressions that return pseudo-types, such as RECORD. Fix for logical replication subscribers for executing per-column UPDATE triggers. Fix for several crashes and failures for logical replication subscribers and publishers. Improve efficiency of logical replication with REPLICA IDENTITY FULL. Ensure that calling pg_replication_slot_advance() on a physical replication slot will persist changes across restarts. Several fixes for the walsender processes. Improve performance of hash joins with very large inner relations. Fix placement of "Subplans Removed" field in EXPLAIN output by placing it with its parent Append or MergeAppend plan. Several fixes for parallel query plans. Several fixes for query planner errors, including one that affected joins to single-row subqueries. Several fixes for MCV extend statistics, including one for incorrect estimation for OR clauses. Improve efficiency of parallel hash join on CPUs with many cores. Ignore the CONCURRENTLY option when performing an index creation, drop, or reindex on a temporary table. Fall back to non-parallel index builds when a parallelized CREATE INDEX has no free dynamic shared memory slots. Several fixes for GiST & GIN indexes. Fix possible crash in BRIN index operations with box, range and inet data types. Fix support for BRIN hypothetical indexes. Fix failure in ALTER TABLE when a column referenced in a GENERATED expression is added or changed in type earlier in the same ALTER TABLE statement. Fix handling of multiple AFTER ROW triggers on a foreign table. Fix off-by-one result for EXTRACT(ISOYEAR FROM timestamp) for BC dates. Prevent unwanted lowercasing and truncation of RADIUS authentication parameters in the pg_hba.conf file. Several fixes for GSSAPI support, including having libpq accept all GSS-related connection parameters even if the GSSAPI code is not compiled in. Several fixes for pg_dump and pg_restore when run in parallel mode. Fix crash with postgres_fdw when trying to execute a remote query on the remote server such as UPDATE remote_tab SET (x,y) = (SELECT ...). Disallow NULL category values in the crosstab() function of contrib/tablefunc to prevent crashes. Several fixes for Windows, including a race condition that could cause timing oddities with NOTIFY. Several ecpg fixes.
Revision 1.6 / (download) - annotate - [select for diffs], Sat Jan 18 21:48:01 2020 UTC (4 years, 3 months ago) by jperkin
Branch: MAIN
Changes since 1.5: +2 -1
lines
Diff to previous 1.5 (colored) to selected 1.22 (colored)
*: Recursive revision bump for openssl 1.1.1.
Revision 1.5 / (download) - annotate - [select for diffs], Fri Nov 9 18:12:24 2018 UTC (5 years, 5 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2019Q4-base,
pkgsrc-2019Q4,
pkgsrc-2019Q3-base,
pkgsrc-2019Q3,
pkgsrc-2019Q2-base,
pkgsrc-2019Q2,
pkgsrc-2019Q1-base,
pkgsrc-2019Q1,
pkgsrc-2018Q4-base,
pkgsrc-2018Q4
Changes since 1.4: +1 -2
lines
Diff to previous 1.4 (colored) to selected 1.22 (colored)
postgresNN: updated to the latest The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, and 9.3.25. This release fixes one security issue as well as bugs reported over the last three months. All users using the affected versions of PostgreSQL should update as soon as possible. Please see the notes on "Updating" below for any post-update steps that may be required if you are using pg_stat_statements in your installation. This update is also the final release for PostgreSQL 9.3, which is now end-of-life and will no longer receive any bug or security fixes. If your environment still uses PostgreSQL 9.3, please make plans to update to a community supported version as soon as possible. Please see our versioning policy for more information. Security Issues One security vulnerability has been closed by this release: CVE-2018-16850: SQL injection in pg_upgrade and pg_dump, via CREATE TRIGGER ... REFERENCING. Versions Affected: 10, 11 Using a purpose-crafted trigger definition, an attacker can run arbitrary SQL statements with superuser privileges when a superuser runs pg_upgrade on the database or during a pg_dump dump/restore cycle. This attack requires a CREATE privilege on some non-temporary schema or a TRIGGER privilege on a table. This is exploitable in the default PostgreSQL configuration, where all users have CREATE privilege on public schema. Bug Fixes and Improvements This update also fixes numerous bugs that were reported in the last several months. Some of these issues affect only version 11, but many affect all supported versions. These releases include fixes that: Ensure that automatically created child indexes are created in the same tablespace as the parent partitioned index Fix several crashes with triggers Fix problems with applying ON COMMIT DELETE ROWS to a partitioned temporary table Fix how NULL values are handled when using LEFT JOIN with a parallelized hash join Several fixes around using named or defaulted arguments in CALL statements Fix for strict aggregate functions (i.e. aggregates that cannot accept NULL inputs) with ORDER BY columns that enforces the strictness check Fix with CASE statements where an expression was cast to an array type Disable an optimization for updating expression indexes in order to prevent a crash Fix a memory leak that occurred on a specific case of using a SP-GiST index Fix for pg_verify_checksums incorrectly reporting on files that are not expected to have checksums Prevent the PostgreSQL server from starting when wal_level is set to a value that cannot support an existing replication slot Ensure that the server will process already-received NOTIFY and SIGTERM interrupts before waiting for client input Allow PL/Ruby to work with newer versions of PostgreSQL Fix for character-class checks on Windows for Unicode characters above U+FFFF, which affected full-text search as well as contrib/ltree and contrib/pg_trgm Fix a case where psql would not report the receipt of a message from a NOTIFY call until after the next command Fix build problems on macOS 10.14 (Mojave) Several build fixes for the Windows platform This updates also contains tzdata release 2018g for DST law changes in Chile, Fiji, Morocco, and Russia (Volgograd), plus historical corrections for China, Hawaii, Japan, Macau, and North Korea.
Revision 1.4 / (download) - annotate - [select for diffs], Wed Aug 22 09:43:23 2018 UTC (5 years, 7 months ago) by wiz
Branch: MAIN
CVS Tags: pkgsrc-2018Q3-base,
pkgsrc-2018Q3
Changes since 1.3: +2 -1
lines
Diff to previous 1.3 (colored) to selected 1.22 (colored)
Recursive bump for perl5-5.28.0
Revision 1.3 / (download) - annotate - [select for diffs], Mon Nov 13 09:33:31 2017 UTC (6 years, 5 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2018Q2-base,
pkgsrc-2018Q2,
pkgsrc-2018Q1-base,
pkgsrc-2018Q1,
pkgsrc-2017Q4-base,
pkgsrc-2017Q4
Changes since 1.2: +1 -2
lines
Diff to previous 1.2 (colored) to selected 1.22 (colored)
postgresql: updated to the latest The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 10.1, 9.6.6, 9.5.10, 9.4.15, 9.3.20, and 9.2.24. This release fixes three security issues. This release also fixes issues found in BRIN indexing, logical replication and other bugs reported over the past three months. All users using the affected versions of PostgreSQL should update as soon as possible. If you use BRIN indexes or contrib/start-scripts, please see the release notes for additional post-upgrade steps. Security Issues Three security vulnerabilities have been fixed by this release: CVE-2017-12172: Start scripts permit database administrator to modify root-owned files CVE-2017-15098: Memory disclosure in JSON functions CVE-2017-15099: INSERT ... ON CONFLICT DO UPDATE fails to enforce SELECT privileges Bug Fixes and Improvements This update also fixes a number of bugs reported in the last few months. Some of these issues affect only version 10, but many affect all supported versions: Fix a race condition in BRIN indexing that could cause some rows to not be included in the indexing. Fix crash when logical decoding is invoked from a PL language function. Several fixes for logical replication. Restored behavior for CTEs attached to INSERT/UPDATE/DELETE statements to pre-version 10. Prevent low-probability crash in processing of nested trigger firings. Do not evaluate an aggregate function's argument expressions when the conditions in the FILTER clause evaluate to FALSE. This complies with SQL-standard behavior. Fix incorrect query results when multiple GROUPING SETS columns contain the same simple variable. Fix memory leak over the lifespan of a query when evaluating a set-returning function from the target list in a SELECT. Several fixes for parallel query execution, including fixing a crash in the parallel execution of certain queries that contain a certain type of bitmap scan. Fix json_build_array(), json_build_object(), jsonb_build_array(), and jsonb_build_object() to handle explicit VARIADIC arguments correctly. Prevent infinite float values from being casted to the numeric type. Fix autovacuum's ãà×Øork itemãàlogic to prevent possible crashes and silent loss of work items. Several fixes for VIEWs around adding columns to the end of a view. Fix for hashability detection of range data types that are created by a user. Improvements on using extended statistics on columns for the purposes of query planning. Prevent idle_in_transaction_session_timeout from being ignored when a statement_timeout occurred earlier. Fix low-probability loss of NOTIFY messages due more than 2 billion transactions processing before any queries are executed in the session. Several file system interaction fixes. Correctly restore the umask setting when file creation fails in COPY or lo_export(). Fix pg_dump to ensure that it emits GRANT commands in a valid order. Fix pg_basebackup's matching of tablespace paths to canonicalize both paths before comparing to help improve Windows compatibility. Fix libpq to not require user's home directory to exist when trying to read the "~/.pgpass" file. Several fixes for ecpg.
Revision 1.2 / (download) - annotate - [select for diffs], Fri Nov 10 14:47:41 2017 UTC (6 years, 5 months ago) by fhajny
Branch: MAIN
Changes since 1.1: +2 -1
lines
Diff to previous 1.1 (colored) to selected 1.22 (colored)
Make sure the --as-needed linker arg does not leak into the pgxs Makefiles on Darwin and SunOS where it's not supported. Bump PKGREVISION on *-client.
Revision 1.1 / (download) - annotate - [select for diffs], Mon Oct 23 20:33:49 2017 UTC (6 years, 5 months ago) by adam
Branch: MAIN
Diff to selected 1.22 (colored)
postgresql10: added version 10.0 Major enhancements in PostgreSQL 10 include: Logical replication using publish/subscribe Declarative table partitioning Improved query parallelism Significant general performance improvements Stronger password authentication based on SCRAM-SHA-256 Improved monitoring and control The above items are explained in more detail in the sections below.