== PostgreSQL Weekly News - June 30, 2019 ==
От | David Fetter |
---|---|
Тема | == PostgreSQL Weekly News - June 30, 2019 == |
Дата | |
Msg-id | 20190630222252.GA6471@fetter.org обсуждение исходный текст |
Список | pgsql-announce |
== PostgreSQL Weekly News - June 30, 2019 == == PostgreSQL Product News == pgBadger v11.0, a PostgreSQL log analyzer and graph tool written in Perl, released. https://github.com/darold/pgbadger/releases repmgr 4.4, a replication manager for PostgreSQL, released. https://repmgr.org/docs/4.4/release-4.4.html pgAdmin4 4.9, a web- and native GUI control center for PostgreSQL, released. https://www.pgadmin.org/docs/pgadmin4/dev/release_notes_4_9.html == PostgreSQL Jobs for June == http://archives.postgresql.org/pgsql-jobs/2019-06/ == PostgreSQL Local == PostgresLondon 2019 will be July 2-3, 2019 with an optional training day on July 1. http://postgreslondon.org PGConf.Brazil 2019 will take place August 1-3, 2019 in São Paulo. http://pgconf.com.br The first Austrian pgDay, will take place September 6, 2019 at the Hilton Garden Inn in Wiener Neustadt. https://pgday.at/en/ PostgresOpen will be September 11th - 13th, 2019 in Orlando, Florida at the Rosen Centre Hotel. The CfP is open at https://2019.postgresopen.org/callforpapers/ https://2019.postgresopen.org/ PostgresConf South Africa 2019 will take place in Johannesburg on October 8-9, 2019 The Call for Papers is open through June 30, 2019. https://postgresconf.org/conferences/SouthAfrica2019 == PostgreSQL in the News == Planet PostgreSQL: http://planet.postgresql.org/ PostgreSQL Weekly News is brought to you this week by David Fetter Submit news and announcements by Sunday at 3:00pm PST8PDT to david@fetter.org. == Applied Patches == Dean Rasheed pushed: - Add security checks to the multivariate MCV estimation code. The multivariate MCV estimation code may run user-defined operators on the values in the MCV list, which means that those operators may potentially leak the values from the MCV list. Guard against leaking data to unprivileged users by checking that the user has SELECT privileges on the table or all of the columns referred to by the statistics. Additionally, if there are any securityQuals on the RTE (either due to RLS policies on the table, or accessing the table via a security barrier view), not all rows may be visible to the current user, even if they have table or column privileges. Thus we further insist that the operator be leakproof in this case. Dean Rasheed, reviewed by Tomas Vondra. Discussion: https://postgr.es/m/CAEZATCUhT9rt7Ui=Vdx4N==VV5XOK5dsXfnGgVOz_JhAicB=ZA@mail.gmail.com https://git.postgresql.org/pg/commitdiff/d7f8d26d9f4c0a574250ec53a03b3dc08d13796c Noah Misch pushed: - Don't call PG_RETURN_BOOL() in a function not returning Datum. This code is new in v12, and the defect probably was not user-visible. https://git.postgresql.org/pg/commitdiff/9a81c9fa3f6a2f57b9db2a1ce5584c85fc1d977e Peter Eisentraut pushed: - Fix breakage introduced in pg_lsn_in(). Using PG_RETURN_LSN() from non-fmgr pg_lsn_in_internal() happened to work on some platforms, but should just be a plain "return". https://git.postgresql.org/pg/commitdiff/2e810508f6b0d89621094445620a1bea3ceff3f1 - Remove explicit error handling for obsolete date/time values. The date/time values 'current', 'invalid', and 'undefined' were removed a long time ago, but the code still contains explicit error handling for the transition. To simplify the code and avoid having to handle these values everywhere, just remove the recognition of these tokens altogether now. Reviewed-by: Michael Paquier <michael@paquier.xyz> https://git.postgresql.org/pg/commitdiff/666cbae16da46b833f57ef8b12ff0bf215684d9c - Don't call data type input functions in GUC check hooks. Instead of calling pg_lsn_in() in check_recovery_target_lsn and timestamptz_in() in check_recovery_target_time, reorganize the respective code so that we don't raise any errors in the check hooks. The previous code tried to use PG_TRY/PG_CATCH to handle errors in a way that is not safe, so now the code contains no ereport() calls and can operate safely within the GUC error handling system. Moreover, since the interpretation of the recovery_target_time string may depend on the time zone, we cannot do the final processing of that string until all the GUC processing is done. Instead, check_recovery_target_time() now does some parsing for syntax checking, but the actual conversion to a timestamptz value is done later in the recovery code that uses it. Reported-by: Andres Freund <andres@anarazel.de> Reviewed-by: Michael Paquier <michael@paquier.xyz> Discussion: https://www.postgresql.org/message-id/flat/20190611061115.njjwkagvxp4qujhp%40alap3.anarazel.de https://git.postgresql.org/pg/commitdiff/21f428ebde39339487c271a830fed135d6032d73 - Update comment. Function was renamed/replaced in c2fe139c201c48f1133e9fbea2dd99b8efe2fadd but the header comment was not updated. https://git.postgresql.org/pg/commitdiff/f2f0082ef5969b57d0b52d0c2e891872ed1b0a51 - Upgrade internal error message to external. As part of REINDEX CONCURRENTLY, this formerly internal-only error message becomes potentially user-visible (see regression tests), so change from errmsg_internal() to errmsg(), and update comment. https://git.postgresql.org/pg/commitdiff/12e037e2090b1a6446376814ea0419463b02c254 - Update unicode_norm_table.h to Unicode 12.1.0. https://git.postgresql.org/pg/commitdiff/82be666ee36842af2a1b81e570bd5578f264de65 - Make script output more pgindent compatible. https://git.postgresql.org/pg/commitdiff/2cadefbb97ff8e5566476780dc200db06af6ba09 - Correct script name in README file. https://git.postgresql.org/pg/commitdiff/eb8d05bfeca416a970cc33af5915ec7b4f4a2f69 - Update comment. Function was renamed/replaced in c2fe139c201c48f1133e9fbea2dd99b8efe2fadd but the header comment was not updated. https://git.postgresql.org/pg/commitdiff/f2f0082ef5969b57d0b52d0c2e891872ed1b0a51 Tom Lane pushed: - Exclude new src/test/modules/unsafe_tests directory from MSVC build. There's nothing to build here, and that was confusing AddContrib(). Per buildfarm. https://git.postgresql.org/pg/commitdiff/c000a47ad1fdd4fb92c7068279d97e0c3db4f8eb - Blind attempt to fix SSPI-auth case in 010_dump_connstr.pl. Up to now, pg_regress --config-auth had a hard-wired assumption that the target cluster uses the default bootstrap superuser name. pg_dump's 010_dump_connstr.pl TAP test uses non-default superuser names, and was klugily getting around the restriction by listing the desired superuser name as a role to "create". This is pretty confusing (or at least, it confused me). Let's make it clearer by allowing --config-auth mode to be told the bootstrap superuser name. Repurpose the existing --user switch for that, since it has no other function in --config-auth mode. Per buildfarm. I don't have an environment at hand in which I can test this fix, but the buildfarm should soon show if it works. Discussion: https://postgr.es/m/3142.1561840611@sss.pgh.pa.us https://git.postgresql.org/pg/commitdiff/681cca86f5071379c4a8599ef9387b666b7e6879 - Move rolenames test out of the core regression tests. This test script is unsafe to run in "make installcheck" mode for (at least) two reasons: it creates and destroys some role names that don't follow the "regress_xxx" naming convention, and it sets and then resets the application_name GUC attached to every existing role. While we've not had complaints, these surely are not good things to do within a production installation, and regress.sgml pretty clearly implies that we won't do them. Rather than lose test coverage altogether, let's just move this script somewhere where it will get run by "make check" but not "make installcheck". src/test/modules/ already has that property. Since it seems likely that we'll want other regression tests in future that also exceed the constraints of "make installcheck", create a generically-named src/test/modules/unsafe_tests/ directory to hold them. Discussion: https://postgr.es/m/16638.1468620817@sss.pgh.pa.us https://git.postgresql.org/pg/commitdiff/c91504b958e1647f87ffb7168e61db75ca09b928 - Fix regression tests to use only global names beginning with "regress_". In commit 18555b132 we tentatively established a rule that regression tests should use names containing "regression" for databases, and names starting with "regress_" for all other globally-visible object names, so as to circumscribe the side-effects that "make installcheck" could have on an existing installation. However, no enforcement mechanism was created, so it's unsurprising that some new violations have crept in since then. In fact, a whole new *category* of violations has crept in, to wit we now also have globally-visible subscription and replication origin names, and "make installcheck" could very easily clobber user-created objects of those types. So it's past time to do something about this. This commit sanitizes the tests enough that they will pass (i.e. not generate any visible warnings) with the enforcement mechanism I'll add in the next commit. There are some TAP tests that still trigger the warnings, but the warnings do not cause test failure. Since these tests do not actually run against a pre-existing installation, there's no need to worry whether they could conflict with user-created objects. The problem with rolenames.sql testing special role names like "user" is still there, and is dealt with only very cosmetically in this patch (by hiding the warnings :-(). What we actually need to do to be safe is to take that test script out of "make installcheck" altogether, but that seems like material for a separate patch. Discussion: https://postgr.es/m/16638.1468620817@sss.pgh.pa.us https://git.postgresql.org/pg/commitdiff/ca129e58c01f29ef24a734313ff315933b3d5b67 - Add an enforcement mechanism for global object names in regression tests. In commit 18555b132 we tentatively established a rule that regression tests should use names containing "regression" for databases, and names starting with "regress_" for all other globally-visible object names, so as to circumscribe the side-effects that "make installcheck" could have on an existing installation. This commit adds a simple enforcement mechanism for that rule: if the code is compiled with ENFORCE_REGRESSION_TEST_NAME_RESTRICTIONS defined, it will emit a warning (not an error) whenever a database, role, tablespace, subscription, or replication origin name is created that doesn't obey the rule. Running one or more buildfarm members with that symbol defined should be enough to catch new violations, at least in the regular regression tests. Most TAP tests wouldn't notice such warnings, but that's actually fine because TAP tests don't execute against an existing server anyway. Since it's already the case that running src/test/modules/ tests in installcheck mode is deprecated, we can use that as a home for tests that seem unsafe to run against an existing server, such as tests that might have side-effects on existing roles. Document that (though this commit doesn't in itself make it any less safe than before). Update regress.sgml to define these restrictions more clearly, and to clean up assorted lack-of-up-to-date-ness in its descriptions of the available regression tests. Discussion: https://postgr.es/m/16638.1468620817@sss.pgh.pa.us https://git.postgresql.org/pg/commitdiff/54100f5c6052404f68de9ce7310ceb61f1c291f8 - Disallow user-created replication origins named "pg_xxx". Since we generate such names internally, it seems like a good idea to have a policy of disallowing them for user use, as we do for many other object types. Otherwise attempts to use them will randomly fail due to collisions with internally-generated names. Discussion: https://postgr.es/m/3606.1561747369@sss.pgh.pa.us https://git.postgresql.org/pg/commitdiff/a1e61badf97bc446053145ba40de6db835678ce3 - Drop test user when done with it. Commit d7f8d26d9 added a test case that created a user, but forgot to drop it again. This is no good; for one thing, it causes repeated "make installcheck" runs to fail. https://git.postgresql.org/pg/commitdiff/f31111bbe81db0e84fb486c6423a234c47091b30 - Further fix ALTER COLUMN TYPE's handling of indexes and index constraints. This patch reverts all the code changes of commit e76de8861, which turns out to have been seriously misguided. We can't wait till later to compute the definition string for an index; we must capture that before applying the data type change for any column it depends on, else ruleutils.c will deliverr wrong/misleading results. (This fine point was documented nowhere, of course.) I'd also managed to forget that ATExecAlterColumnType executes once per ALTER COLUMN TYPE clause, not once per statement; which resulted in the code being basically completely broken for any case in which multiple ALTER COLUMN TYPE clauses are applied to a table having non-constraint indexes that must be rebuilt. Through very bad luck, none of the existing test cases nor the ones added by e76de8861 caught that, but of course it was soon found in the field. The previous patch also had an implicit assumption that if a constraint's index had a dependency on a table column, so would the constraint --- but that isn't actually true, so it didn't fix such cases. Instead of trying to delete unneeded index dependencies later, do the is-there-a-constraint lookup immediately on seeing an index dependency, and switch to remembering the constraint if so. In the unusual case of multiple column dependencies for a constraint index, this will result in duplicate constraint lookups, but that's not that horrible compared to all the other work that happens here. Besides, such cases did not work at all before, so it's hard to argue that they're performance-critical for anyone. Per bug #15865 from Keith Fiske. As before, back-patch to all supported branches. Discussion: https://postgr.es/m/15865-17940eacc8f8b081@postgresql.org https://git.postgresql.org/pg/commitdiff/f946a409143d01951411382fbc3c91c7eb640094 - Purely-cosmetic adjustments in tablecmds.c. Move ATExecAlterColumnGenericOptions away from where it was unthinkingly dropped, in the middle of a lot of ALTER COLUMN TYPE code. I don't have any high principles about where to put it instead, so let's just put it after ALTER COLUMN TYPE and before ALTER OWNER, matching existing decisions about how to order related code stanzas. Also add the minimal function header comment that the original author was too cool to bother with. Along the way, upgrade header comments for nearby ALTER COLUMN TYPE functions. Discussion: https://postgr.es/m/14787.1561403130@sss.pgh.pa.us https://git.postgresql.org/pg/commitdiff/ccfcc8fdbd9bdbfd18fda5d7c698af8d175f5319 - Follow the rule that regression-test-created roles are named "regress_xxx". Commit 1c5d9270e had not gotten the word about this. (For previous context, see 18555b132.) https://git.postgresql.org/pg/commitdiff/c360477d2e2f65fdea64aa8bc94a6286d0883f7a - Follow the rule that regression-test-created roles are named "regress_xxx". contrib/amcheck didn't get the memo either. https://git.postgresql.org/pg/commitdiff/65e6d42140c8d9918638b9f73528288ab980af82 Peter Geoghegan pushed: - Correct obsolete amcheck comments. Oversight in commit dd299df8. https://git.postgresql.org/pg/commitdiff/b00326df7ad4ab7d21aad3b6fe6558ea6b61897d Thomas Munro pushed: - Remove misleading comment from pathnodes.h. As of commit e5253fdc, it is no longer true that the leader always executes the subplan of a Gather Merge node. Remove comment to that effect. Back-patch to 11. Discussion: https://postgr.es/m/CA%2BhUKGJEaZJYezXAOutuiWT%2BfxCA44%2BoKtVPAND2ubLiigR%3D-w%40mail.gmail.com https://git.postgresql.org/pg/commitdiff/a2dec374807565f6337915fb236bb3ae37af0644 - Don't unset MAKEFLAGS in non-GNU Makefile. It's useful to be able to pass down options like -s and -j. Back-patch to 9.5, like commit a76200de. Discussion: https://postgr.es/m/CA%2BhUKG%2Be1M8-BbL%3DPqhTp6oO6XPO6%2Bs9WGQMLfbuZ%3DG9CtzyXg%40mail.gmail.com https://git.postgresql.org/pg/commitdiff/0089c3059cb6b3dd20cf072f26d1a7a33412df39 Michaël Paquier pushed: - Remove unnecessary header from be-secure-gssapi.c. libpq/libpq-be.h is included by libpq/libpq.h so there is no need to explicitly include it separately. Author: Daniel Gustafsson Reviewed-by: Julien Rouhaud Discussion: https://postgr.es/m/A4852E46-9ED1-4861-A23B-22A83E34A084@yesql.se https://git.postgresql.org/pg/commitdiff/c0faa727507ed34db0d02769d21bbaaf9605e2e4 - Add toast-level reloption for vacuum_index_cleanup. a96c41f has introduced the option for heap, but it still lacked the variant to control the behavior for toast relations. While on it, refactor the tests so as they stress more scenarios with the various values that vacuum_index_cleanup can use. It would be useful to couple those tests with pageinspect to check that pages are actually cleaned up, but this is left for later. Author: Masahiko Sawada, Michael Paquier Reviewed-by: Peter Geoghegan Discussion: https://postgr.es/m/CAD21AoCqs8iN04RX=i1KtLSaX5RrTEM04b7NHYps4+rqtpWNEg@mail.gmail.com https://git.postgresql.org/pg/commitdiff/ce59b75d449d9152667ce3e9eab33ef2872bfd98 - Add support for OpenSSL 1.1.0 and newer versions in MSVC scripts. Up to now, the MSVC build scripts are able to support only one fixed version of OpenSSL, and they lacked logic to detect the version of OpenSSL a given compilation of Postgres is linking to (currently 1.0.2, the latest LTS of upstream which will be EOL'd at the end of 2019). This commit adds more logic to detect the version of OpenSSL used by a build and makes use of it to add support for compilation with OpenSSL 1.1.0 which requires a new set of compilation flags to work properly. The supported OpenSSL installers have changed their library layer with various library renames with the upgrade to 1.1.0, making the logic a bit more complicated. The scripts are now able to adapt to the new world order. Reported-by: Sergey Pashkov Author: Juan José Santamaría Flecha, Michael Paquier Reviewed-by: Álvaro Herrera Discussion: https://postgr.es/m/15789-8fc75dea3c5a17c8@postgresql.org https://git.postgresql.org/pg/commitdiff/d993e0fb82ffaa15be72c1ac10403bfa06708069 - Remove remaining traces of Rand_OpenSSL() from the tree. fe0a0b5 has removed the last use of this routine from pgcrypto, leading to a useless symbol definition and an extra configure check. Author: Michael Paquier Reviewed-by: Daniel Gustafsson, Tom Lane Discussion: https://postgr.es/m/20190626142544.GN1714@paquier.xyz https://git.postgresql.org/pg/commitdiff/322c5bfdc3d76f6463768ecd8fced30c881b8be5 Álvaro Herrera pushed: - Fix for dropped columns in a partitioned table's default partition. We forgot to map column numbers to/from the default partition for various operations, leading to valid cases failing with spurious errors, such as ERROR: attribute N of type some_partition has been dropped It was also possible that the search for conflicting rows in the default partition when attaching another partition would fail to detect some. Secondarily, it was also possible that such a search should be skipped (because the constraint was implied) but wasn't. Fix all this by mapping column numbers when necessary. Reported by: Daniel Wilches Author: Amit Langote Discussion: https://postgr.es/m/15873-8c61945d6b3ef87c@postgresql.org https://git.postgresql.org/pg/commitdiff/23cccb17fe0bbb5df86780da5c346cc060c21421 - Fix partitioned index creation with foreign partitions. When a partitioned tables contains foreign tables as partitions, it is not possible to implement unique or primary key indexes -- but when regular indexes are created, there is no reason to do anything other than ignoring such partitions. We were raising errors upon encountering the foreign partitions, which is unfriendly and doesn't protect against any actual problems. Relax this restriction so that index creation is allowed on partitioned tables containing foreign partitions, becoming a no-op on them. (We may later want to redefine this so that the FDW is told to create the indexes on the foreign side.) This applies to CREATE INDEX, as well as ALTER TABLE / ATTACH PARTITION and CREATE TABLE / PARTITION OF. Backpatch to 11, where indexes on partitioned tables were introduced. Discussion: https://postgr.es/m/15724-d5a58fa9472eef4f@postgresql.org Author: Álvaro Herrera Reviewed-by: Amit Langote https://git.postgresql.org/pg/commitdiff/55ed3defc966cf718fe1e8c0efe964580bb23351 - Fix use-after-free introduced in 55ed3defc966. Evidenced by failure under RELCACHE_FORCE_RELEASE (buildfarm member prion). Author: Amit Langote Discussion: https://postgr.es/m/CA+HiwqGV=k_Eh4jBiQw66ivvdG+EUkrEYeHTYL1SvDj_YOYV0g@mail.gmail.com https://git.postgresql.org/pg/commitdiff/050098b14e33a5d3dfabf172ebbddd20c6bb4665 Tomáš Vondra pushed: - Update reference to sampling algorithm in analyze.c. Commit 83e176ec1 moved row sampling functions from analyze.c to utils/misc/sampling.c, but failed to update comment referring to the sampling algorithm from Jeff Vitter's paper. Correct the comment by pointing to utils/misc/sampling.c. Author: Etsuro Fujita Discussion: https://postgr.es/m/CAPmGK154gp%2BQd%3DcorQOv%2BPmbyVyZBjp_%2Bhb766UJeD1e_ie6XQ%40mail.gmail.com https://git.postgresql.org/pg/commitdiff/69fd82fedd746b82427097883daf2921dd77584e == Pending Patches == Peter Eisentraut sent in another revision of a patch to add a CREATE DATABASE LOCALE option. James Coleman sent in a patch to correct the assertion comment in tuplesort_set_bound. Peter Eisentraut sent in a patch to run the UTF8-requiring collation tests by default. Peter Eisentraut sent in another revision of a patch to use explicit_bzero. Takeshi Ideriha sent in another revision of a patch to implement shared memory context backed by DSA. Thomas Munro sent in a patch to remove a misleading comment from pathnodes.h. Ashwin Agrawal sent in a patch to remove the HeapTuple and buffer dependency for predicate locking functions. Amit Khandekar sent in two more revisions of a patch to implement minimal logical decoding on standbys. James Coleman and Tomáš Vondra traded patches to implement incremental sort. John Naylor sent in three more revisions of a patch to simplify flex. Andrey Borodin sent in two more revisions of a patch to improve the performance of pglz. Tomáš Vondra sent in two revisions of a patch to rework PG MCV list items. Binguo Bao sent in another revision of a patch to optimize partial TOAST decompression. Thomas Munro sent in a patch to cache the result of RelationHasUnloggedIndex(). Ildar Musin sent in a patch to fix a duplicated LSN in ReorderBuffer. Tom Lane sent in a patch to simplify \d index sort order in psql. Tom Lane sent in a patch to avoid COMPLETE_FROM_CONST in psql. Peter Eisentraut sent in a patch to handle fsync failures in pg_receivewal and pg_recvlogical. Amit Kapila sent in another revision of a patch to clean up orphaned files using undo logs. Liudmila Mantrova sent in another revision of a patch to clarify the JSONPATH docs. Peter Eisentraut sent in a patch to add an errbacktrace() function and corresponding backtrace_function GUC. Pavel Stěhule sent in another revision of a patch to implement DROP DATABASE FORCE, along with a corresponding option for dropdb. Fabien COELHO sent in another revision of a patch to implement SHOW_ALL_RESULTS in psql. Zheng Li sent in two more revisions of a patch to turn NOT IN into an anti-JOIN where possible. Ryohei Nagaura sent in a patch to add socket_timeout to libpq. David Rowley sent in another revision of a patch to shrink bloated locallocktable. Yuzuko Hosoya sent in another revision of a patch to fix pruning of default partitions and ignore contradictory where clauses at the partprune step. David Rowley sent in a patch to do runtime pruning for ModifyTable. Andrey V. Lepikhov sent in another revision of a patch to remove unneeded self-joins. Michaël Paquier sent in another revision of a patch to add support for building with MSVC 2019. Surafel Temesgen sent in another revision of a patch to add a PERCENT option to FETCH FIRST. Artur Zakirov sent in a patch to remove a redundant quote_all_identifiers from _dumpOptions. Peter Eisentraut sent in a patch to use relative rpath if possible. Didier sent in a patch to replace the TupleDescAttr macro with a static inline function with AssertArg. Daniel Gustafsson sent in a patch to replace the OpenSSL-specific value under USE_SSL with USE_OPENSSL. Jesper Pedersen sent in a patch to document the fact that pg_receivewal doesn't acknowledge that the WAL has been applied. Jehan-Guillaume de Rorthais sent in another revision of a patch to add a WAL relief valve for replication slots. Heikki Linnakangas sent in another revision of a patch to refactor the checks for deleted GiST pages and Use full 64-bit XID for checking whether a deleted GiST page is old enough. Tomáš Vondra sent in two revisions of a patch to rework MCV serialization. Peter Eisentraut sent in another revision of a patch to add a new and improved allow_system_table_ddl setting. Etsuro Fujita sent in a patch to remove a redundancy from postgresAcquireSampleRowsFunc. Yugo Nagata sent in another revision of a patch to implement incremental view maintenance. Surafel Temesgen sent in another revision of a patch to handle conflicts in COPY FROM. Noah Misch sent in another revision of a patch to prevent concurrent SimpleLruTruncate() for any given SLRU. Luis Carril sent in a patch to add an option to pg_dump to include data in foreign tables. Julien Rouhaud sent in two more revisions of a patch to add a queryId to the pg_catalog.pg_stat_activity view. Julien Rouhaud sent in another revision of a patch to clean up and refactor reindexdb.c. Julien Rouhaud and Nikita Glukhov traded patches to avoid full GIN index scans when possible. Justin Pryzby sent in another revision of a patch to print the table associated with a given TOAST table in psql's \d output. Pavel Stěhule sent in two revisions of a patch to add an option to sort by size in psql. Masahiko Sawada sent in another revision of a patch to implement transparent data encryption and a key management service. Peter Eisentraut sent in a patch to rearrange base backup client as an auxiliary backend process, simplifying operation of same. Tomáš Vondra sent in a patch to increase the default value of effective_io_concurrency. Tomáš Vondra sent in a patch to implement ALTER STATISTICS ... SET STATISTICS ... Pavel Stěhule sent in another revision of a patch to implement schema variables. Julien Rouhaud sent in a patch to add parallelism and glibc dependent only options to reindexdb. Alexander Lakhin sent in a patch to fix some typos and inconsistencies. Tom Lane sent in another revision of a patch to remove conversions from and to SQL_ASCII.
В списке pgsql-announce по дате отправления: