== PostgreSQL Weekly News - July 01 2018 ==
| От | David Fetter |
|---|---|
| Тема | == PostgreSQL Weekly News - July 01 2018 == |
| Дата | |
| Msg-id | 20180701210914.GA30643@fetter.org обсуждение исходный текст |
| Список | pgsql-announce |
== PostgreSQL Weekly News - July 01 2018 == PostgreSQL 11 Beta 2 released. Test! https://www.postgresql.org/about/news/1867/ == PostgreSQL Product News == pgAdmin4 3.1, a web- and native GUI control center for PostgreSQL, released. https://www.pgadmin.org/docs/pgadmin4/dev/release_notes_3_1.html == PostgreSQL Jobs for July == http://archives.postgresql.org/pgsql-jobs/2018-07/ == PostgreSQL Local == pgConf UK 2018 will be held on July 3, 2018 in London. http://www.pgconf.uk/ PGConf.Brazil 2018 will take place in São Paulo, Brazil on August 3-4 2018. http://pgconf.com.br PgConf Silicon Valley 2018 will be held in San Francisco on September 5-7, 2018. https://2018.postgresopen.org/ The Portland PostgreSQL Users Group will be holding a PGDay on September 10, 2018 in Portland, OR. The CfP is open at https://goo.gl/forms/E0CiUQGSZGMYwh922 https://pdx.postgresql.us/pdxpgday2018 PostgresConf South Africa 2018 will take place in Johannesburg on October 9, 2018 https://postgresconf.org/conferences/SouthAfrica2018 PostgreSQL Conference Europe 2018 will be held on October 23-26, 2018 at the Lisbon Marriott Hotel in Lisbon, Portugal. The CfP is open through August 6, 2018 midnight CET at https://2018.pgconf.eu/callforpapers https://2017.pgconf.eu/ 2Q PGConf will be on December 4-5, 2018 in Chicago, IL. The CfP is open through August 27, 2018 at midnight Pacific Time at http://www.2qpgconf.com/#cfp http://www.2qpgconf.com/ PGConf.ASIA 2018 will take place on December 10-12, 2018 in Akihabara, Tokyo, Japan. The CfP is open until midnight, July 31, 2018, Japan time at pgconf-asia-2018-submission(at)pgconf(dot)asia http://www.pgconf.asia/EN/2018/ == 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 == Michaël Paquier pushed: - Address set of issues with errno handling. System calls mixed up in error code paths are causing two issues which several code paths have not correctly handled: 1) For write() calls, sometimes the system may return less bytes than what has been written without errno being set. Some paths were careful enough to consider that case, and assumed that errno should be set to ENOSPC, other calls missed that. 2) errno generated by a system call is overwritten by other system calls which may succeed once an error code path is taken, causing what is reported to the user to be incorrect. This patch uses the brute-force approach of correcting all those code paths. Some refactoring could happen in the future, but this is let as future work, which is not targeted for back-branches anyway. Author: Michael Paquier Reviewed-by: Ashutosh Sharma Discussion: https://postgr.es/m/20180622061535.GD5215@paquier.xyz https://git.postgresql.org/pg/commitdiff/6cb3372411fd6ed8ba0f8d36ae578a2daa517c16 - Correct handling of fsync failures with tar mode of walmethods.c. This file has been missing the fact that it needs to report back to callers a proper failure on fsync calls. I have spotted the one in tar_finish() while Kuntal has spotted the one in tar_close(). Backpatch down to 10 where this code has been introduced. Reported by: Michael Paquier, Kuntal Ghosh Author: Michael Paquier Reviewed-by: Kuntal Ghosh, Magnus Hagander Discussion: https://postgr.es/m/20180625024356.GD1146@paquier.xyz https://git.postgresql.org/pg/commitdiff/d08c3d5197fac1f49cedbd8417e685479ad7439a - Fix description and documentation related to pg_restore --no-comments. These descriptions have been referring to object dump, but a restore operation is done. Reported-by: Andrey Lizenko Author: Andrey Lizenko Discussion: https://postgr.es/m/152992021588.1268.16786093506650391435@wrigleys.postgresql.org https://git.postgresql.org/pg/commitdiff/c672d709b089f919381a2c36eea32a29d8de4198 - Make capitalization of term "OpenSSL" more consistent. This includes code comments and documentation. No backpatch as this is cosmetic even if there are documentation changes which are user-facing. Author: Daniel Gustafsson Discussion: https://postgr.es/m/BB89928E-2BC7-489E-A5E4-6D204B3954CF@yesql.se https://git.postgresql.org/pg/commitdiff/dad5f8a3d51c8b12bfa0d2c635639fff9fad5155 - Replace search.cpan.org with metacpan.org. search.cpan.org has been EOL'd, with metacpan.org being the official replacement to which URLs now redirect. Update links to match the new URL. Also update links to CPAN to use https as it will redirect from http. Author: Daniel Gustafsson Discussion: https://postgr.es/m/B74C0219-6BA9-46E1-A524-5B9E8CD3BDB3@yesql.se https://git.postgresql.org/pg/commitdiff/dad335b89f2e1d543ef8226b7de4b191246a06dd - Use optimized bitmap set function for membership test in postgres_fdw. Deparsing logic in postgres_fdw for locking, FROM clause (alias) and Var (column qualification) does not need to know the exact number of members involved, which can be calculated with bms_num_members(), but just if there is more than one relation involved, which is what bms_membership() does. The latter is more performant than the former so this shaves a couple of cycles. Author: Daniel Gustafsson Reviewed-by: Ashutosh Bapat, Nathan Bossart Discussion: https://postgr.es/m/C73594E0-2B67-4E10-BB35-CDE0E41CC384@yesql.se https://git.postgresql.org/pg/commitdiff/65782346a4812482bfb09f9e1117c908146e67b5 - Add tests for inheritance trees mixing permanent and temporary relations. While working on 1c7c317c and related things, which has clarified the use of partitions with temporary tables, I have noticed that there could be better coverage for inheritance trees mixing temporary and permanent relations. A lot of cross-checks happen in MergeAttributes() which is not designed for this purpose, so the tests added in this commit will make sure that any kind of future refactoring will limit the amount of compatibility breakage. Author: Michael Paquier Reviewed-by: Ashutosh Bapat Discussion: https://postgr.es/m/20180619022131.GE3314@paquier.xyz https://git.postgresql.org/pg/commitdiff/9994013ff32cb8371aed8ba28fc262e0a8cb0b4b Peter Eisentraut pushed: - Translation updates. Source-Git-URL: https://git.postgresql.org/git/pgtranslation/messages.git Source-Git-Hash: 884f33d735870f94357820800840af3e93ff4628 https://git.postgresql.org/pg/commitdiff/299addd592ccf36d495319bda0f14049548ee130 - Reword SPI_ERROR_TRANSACTION errors in PL/pgSQL. The previous message for SPI_ERROR_TRANSACTION claimed "cannot begin/end transactions in PL/pgSQL", but that is no longer true. Nevertheless, the error can still happen, so reword the messages. The error cases in exec_prepare_plan() could never happen, so remove them. https://git.postgresql.org/pg/commitdiff/c9301deb9bf86aaf9144a66026bc121a3eededee - doc: Document some nuances of logical replication of TRUNCATE. https://git.postgresql.org/pg/commitdiff/c9d6a45724d642a00bd2b4c0f082cf4e1eb76e29 - Fix whitespace. https://git.postgresql.org/pg/commitdiff/0fcf5e0e6e7a353f862504da0a321f148ad2de03 - doc: Improve wording and fix whitespace. https://git.postgresql.org/pg/commitdiff/ae5ed75ed4a951c58ec6a76362241b6ac32be61c - doc: Replace non-ASCII lines in psql example output. https://git.postgresql.org/pg/commitdiff/539f32bdd6915e950d225e732959a1b068598993 - Documentation spell checking and markup improvements. https://git.postgresql.org/pg/commitdiff/f7481d2c3c52042030269b91bfeb00f120adb618 - Use $Test::Builder::Level in TAP test functions. In TAP test functions, that is, those that produce test results, locally increment $Test::Builder::Level. This has the effect that test failures are reported at the callers location rather than somewhere in the test support libraries. Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi> https://git.postgresql.org/pg/commitdiff/c4309f4aeeae54e4c5281d68e29288af1d0d1ed2 - Fix libpq example programs. When these programs call pg_catalog.set_config, they need to check for PGRES_TUPLES_OK instead of PGRES_COMMAND_OK. Fix for 5770172cb0c9df9e6ce27c507b449557e5b45124. Reported-by: Ideriha, Takeshi <ideriha.takeshi@jp.fujitsu.com> https://git.postgresql.org/pg/commitdiff/7bdea6263543c0dabf4d374b3c8d2c3a1d91649e - pg_standby: Remove code for .backup files. These files are no longer requested on recovery (since 06f82b29616cd9effcaefd99c6b6e2e80697482f), so the code for handling them here is useless. Author: Yugo Nagata <nagata@sraoss.co.jp> https://git.postgresql.org/pg/commitdiff/a33969ee918aafdb9086be27d7d63b129b4bfc44 Álvaro Herrera pushed: - Stamp 11beta2. https://git.postgresql.org/pg/commitdiff/1d4e5edc1dc22f00a0abb00ed9b56c08c4a1f599 - Update obsolete comments. Commit 9fab40ad32ef removed some pre-allocating logic in reorderbuffer.c, but left outdated comments in place. Repair. Author: Álvaro Herrera https://git.postgresql.org/pg/commitdiff/322548a8abe225f2cfd6a48e07b99e2711d28ef7 - Allow direct lookups of AppendRelInfo by child relid. find_appinfos_by_relids had quite a large overhead when the number of items in the append_rel_list was high, as it had to trawl through the append_rel_list looking for AppendRelInfos belonging to the given childrelids. Since there can only be a single AppendRelInfo for each child rel, it seems much better to store an array in PlannerInfo which indexes these by child relid, making the function O(1) rather than O(N). This function was only called once inside the planner, so just replace that call with a lookup to the new array. find_childrel_appendrelinfo is now unused and thus removed. This fixes a planner performance regression new to v11 reported by Thomas Reiss. Author: David Rowley Reported-by: Thomas Reiss Reviewed-by: Ashutosh Bapat Reviewed-by: Álvaro Herrera Discussion: https://postgr.es/m/94dd7a4b-5e50-0712-911d-2278e055c622@dalibo.com https://git.postgresql.org/pg/commitdiff/7d872c91a3f9d49b56117557cdbb0c3d4c620687 - Enable failure to rename a partitioned index. Concurrently with partitioned index development (commit 8b08f7d4820f), the code to handle failure to rename indexes was refactored (commit 8b9e9644dc6a). Turns out that that particular case was untested, which naturally led it to be broken. Add tests and the missing code line. Co-authored-by: David Rowley <dgrowley@gmail.com> Co-authored-by: Álvaro Herrera <alvherre@alvh.no-ip.org> Reported-by: Rajkumar Raghuwanshi <rajkumar.raghuwanshi@enterprisedb.com> Discussion: https://postgr.es/m/CAKcux6mfYMS3OX0ywjOiWiGSEKhJf-1zdeTceHFbd0mScUzU5A@mail.gmail.com https://git.postgresql.org/pg/commitdiff/040da42367a5de448ddecf6ee7c09f73580a6b28 - Fix typo in comment. Author: Amit Langote Discussion: https://postgr.es/m/b23dc88b-df41-ef07-22c5-12f77cf73b57@lab.ntt.co.jp https://git.postgresql.org/pg/commitdiff/f5545287dc5f565b091f2312684d14fda0705a9a - psql: show cloned triggers in partitions. In a partition, row triggers that had been cloned from their parent partitioned table would not be listed at all in psql's \d, which could surprise users, per insistent complaint from Ashutosh Bapat (though his aim was elsewhere). The simplest possible fix, suggested by Peter Eisentraut, seems to be to list triggers marked as internal if they have a row in pg_depend that points to some other trigger. Author: Álvaro Herrera Discussion: https://postgr.es/m/20180618165910.p26vhk7dpq65ix54@alvherre.pgsql https://git.postgresql.org/pg/commitdiff/bc87f22ef6ef1137909ed7363976c67cf1efa7da - Fix "base" snapshot handling in logical decoding. Two closely related bugs are fixed. First, xmin of logical slots was advanced too early. During xl_running_xacts processing, xmin of the slot was set to the oldest running xid in the record, but that's wrong: actually, snapshots which will be used for not-yet-replayed transactions might consider older txns as running too, so we need to keep xmin back for them. The problem wasn't noticed earlier because DDL which allows to delete tuple (set xmax) while some another not-yet-committed transaction looks at it is pretty rare, if not unique: e.g. all forms of ALTER TABLE which change schema acquire ACCESS EXCLUSIVE lock conflicting with any inserts. The included test case (test_decoding's oldest_xmin) uses ALTER of a composite type, which doesn't have such interlocking. To deal with this, we must be able to quickly retrieve oldest xmin (oldest running xid among all assigned snapshots) from ReorderBuffer. To fix, add another list of ReorderBufferTXNs to the reorderbuffer, where transactions are sorted by base-snapshot-LSN. This is slightly different from the existing (sorted by first-LSN) list, because a transaction can have an earlier LSN but a later Xmin, if its first record does not obtain an xmin (eg. xl_xact_assignment). Note this new list doesn't fully replace the existing txn list: we still need that one to prevent WAL recycling. The second issue concerns SnapBuilder snapshots and subtransactions. SnapBuildDistributeNewCatalogSnapshot never assigned a snapshot to a transaction that is known to be a subtxn, which is good in the common case that the top-level transaction already has one (no point in doing so), but a bug otherwise. To fix, arrange to transfer the snapshot from the subtxn to its top-level txn as soon as the kinship gets known. test_decoding's snapshot_transfer verifies this. Also, fix a minor memory leak: refcount of toplevel's old base snapshot was not decremented when the snapshot is transferred from child. Liberally sprinkle code comments, and rewrite a few existing ones. This part is my (Álvaro's) contribution to this commit, as I had to write all those comments in order to understand the existing code and Arseny's patch. Reported-by: Arseny Sher <a.sher@postgrespro.ru> Diagnosed-by: Arseny Sher <a.sher@postgrespro.ru> Co-authored-by: Arseny Sher <a.sher@postgrespro.ru> Co-authored-by: Álvaro Herrera <alvherre@alvh.no-ip.org> Reviewed-by: Antonin Houska <ah@cybertec.at> Discussion: https://postgr.es/m/87lgdyz1wj.fsf@ars-thinkpad https://git.postgresql.org/pg/commitdiff/f49a80c481f74fa81407dce8e51dea6956cb64f8 - Fix crash when ALTER TABLE recreates indexes on partitions. The skip_build flag was not being passed correctly when recursing to indexes on partitions, leading to attempts to rebuild indexes when they were not yet ready to be rebuilt. Reported-by: Rajkumar Raghuwanshi Discussion: https://postgr.es/m/CAKcux6mxNCGsgATwf5CGMF8g4WSupCXicCVMeKUTuWbyxHOMsQ@mail.gmail.com https://git.postgresql.org/pg/commitdiff/41372071dfaab97a1a8dca83e32b88413460f477 Thomas Munro pushed: - Move RecoveryLockList into a hash table. Standbys frequently need to release all locks held by a given xid. Instead of searching one big list linearly, let's create one list per xid and put them in a hash table, so we can find what we need in O(1) time. Earlier analysis and a prototype were done by David Rowley, though this isn't his patch. Back-patch all the way. Author: Thomas Munro Diagnosed-by: David Rowley, Andres Freund Reviewed-by: Andres Freund, Tom Lane, Robert Haas Discussion: https://postgr.es/m/CAEepm%3D1mL0KiQ2KJ4yuPpLGX94a4Ns_W6TL4EGRouxWibu56pA%40mail.gmail.com Discussion: https://postgr.es/m/CAKJS1f9vJ841HY%3DwonnLVbfkTWGYWdPN72VMxnArcGCjF3SywA%40mail.gmail.com https://git.postgresql.org/pg/commitdiff/a40cff8956e842f737739d93a7b160f0b4a03d13 Fujii Masao pushed: - Fix documentation bug related to backup history file. The backup history file has been no longer necessary for recovery since the version 9.0. It's now basically just for informational purpose. But previously the documentations still described that a recovery requests the backup history file to proceed. The commit fixes this documentation bug. Back-patch to all supported versions. Author: Yugo Nagata Reviewed-by: Kyotaro Horiguchi Discussion: https://postgr.es/m/20180626174752.0ce505e3.nagata@sraoss.co.jp https://git.postgresql.org/pg/commitdiff/bbbbc2f8f3f7d628c74317959a2cfe71fea05575 Peter Geoghegan pushed: - Remove obsolete comment block in nbtsort.c. Building a new nbtree index through incremental insertions would always be slower than our actual approach of sorting using tuplesort, assembling leaf pages from tuplesort output, and writing and WAL-logging whole pages. Remove a comment block from the Berkeley days claiming that incremental insertions might be slightly faster with presorted input. Discussion: https://postgr.es/m/CAH2-WzmKs4mLAoFgJ3yHMRYc849efc=dw+pNRb3NEog2oJoCNw@mail.gmail.com https://git.postgresql.org/pg/commitdiff/cdc2693a11b341043f33e1efc36debe0348fb361 - Correct a comment on logtape.c's leader tape. randomAccess parallel tuplesorts are disallowed because the leader would try to write to its own leader tape, not because the leader would try to write to a worker tape directly. Cleanup from commit 9da0cc35284. https://git.postgresql.org/pg/commitdiff/aefb0a382c10877867d831afe8a292aa355c5a68 Alexander Korotkov pushed: - Increase upper limit for vacuum_cleanup_index_scale_factor. Upper limits for vacuum_cleanup_index_scale_factor GUC and reloption were initially set to 100.0 in 857f9c36. However, after further discussion, it appears that some users like to disable B-tree cleanup index scan completely (assuming there are no deleted pages). vacuum_cleanup_index_scale_factor is used barely to protect against stalled index statistics. And after detailed consideration it appears that risk of stalled index statistics is low. And it would be nice to allow advanced users setting higher values of vacuum_cleanup_index_scale_factor. So, set upper limit for these GUC and reloption to DBL_MAX. Author: Alexander Korotkov Reviewed-by: Masahiko Sawada Discussion: https://postgr.es/m/CAC8Q8tJCb%3DgxhzcV7T6ctx7PY-Ux1oA-AsTJc6cAVNsQiYcCzA%40mail.gmail.com https://git.postgresql.org/pg/commitdiff/6ca33a885bf892a7fa34020a2620c83ccec3cdd7 - Fix upper limit for vacuum_cleanup_index_scale_factor. 6ca33a88 sets upper limit for vacuum_cleanup_index_scale_factor to DBL_MAX. DBL_MAX appears to be platform-dependent. That causes many buildfarm animals to fail, because we check boundaries of vacuum_cleanup_index_scale_factor in regression tests. This commit changes upper limit from DBL_MAX to just "large enough" limit, which was arbitrary selected as 1e10. Author: Alexander Korotkov Reported-by: Tom Lane, Darafei Praliaskouski Discussion: https://postgr.es/m/CAPpHfdvewmr4PcpRjrkstoNn1n2_6dL-iHRB21CCfZ0efZdBTg%40mail.gmail.com Discussion: https://postgr.es/m/CAC8Q8tLYFOpKNaPS_E7V8KtPdE%3D_TnAn16t%3DA3LuL%3DXjfOO-BQ%40mail.gmail.com https://git.postgresql.org/pg/commitdiff/4d54543efa5eb074ead4d0fadb2af4161c943044 Bruce Momjian pushed: - doc: PG 11 relnotes: remove channel binding from major features. Also move to the source code section, and expand the paragraph https://git.postgresql.org/pg/commitdiff/a89357e2f7839f5bc0815f4cf9e565cd3ad7a185 Amit Kapila pushed: - Cosmetic improvements for faster column addition. Changed the name of few structure members for the sake of clarity and removed spurious whitespace. Reported-by: Amit Kapila Author: Amit Kapila, based on suggestion by Andrew Dunstan Reviewed-by: Alvaro Herrera Discussion: https://postgr.es/m/CAA4eK1K2znsFpC+NQ9A4vxT4uDxADN4RmvHX0L6Y=aHVo9gB4Q@mail.gmail.com https://git.postgresql.org/pg/commitdiff/8121ab88e7dfe6ebe56c58257733354cb85f092c - Fix thinko in comments. A slot can not be stored in a tuple but it's vice versa. Reported-by: Ashutosh Bapat Author: Ashutosh Bapat Reviewed-by: Amit Kapila Discussion: https://postgr.es/m/CAFjFpRcHhNhXdegyJv3KKDWrwO1_NB_KYZM_ZSDeMOZaL1A5jQ@mail.gmail.com https://git.postgresql.org/pg/commitdiff/2e61c50785a0dca6ed30a1a5522457b18bbb5498 Andres Freund pushed: - Remove duplicated return statement from llvmjit code. The duplicated return clearly doesn't make sense / isn't reachable. Likely introduced by me (Andres), while revising the code. Author: Rushabh Lathia Discussion: https://postgr.es/m/CAGPqQf2raxWOcbuTP36M1rEF3=Rfo7oD29K3psdyHMeE5swBRg@mail.gmail.com https://git.postgresql.org/pg/commitdiff/986070872ffaae5d9d0e39eddcc952bc261982a2 - Change pqformat.h's integer handling functions to take unsigned integers. As added in 1de09ad8eb1fa673ee7899d6dfbb2b49ba204818 the new functions all accept signed integers as parameters. That's not great, because it's perfectly reasonable to call them with unsigned parameters. Unfortunately unsigned to signed conversion is not well defined, when exceeding the range of the signed value. That's presently not a practical issue in postgres (among other reasons because we force gcc's hand with -fwrapv). But it's clearly not quite right. Thus change the signatures to accept unsigned integers instead, signed to unsigned conversion is always well defined. Also change the backward compat pq_sendint() - while it's deprecated it seems better to be consistent. Per discussion between Andrew Gierth, Michael Paquier, Alvaro Herrera and Tom Lane. Reported-By: Andrew Gierth Author: Andres Freund Discussion: https://postgr.es/m/87r2m10zm2.fsf@news-spur.riddles.org.uk https://git.postgresql.org/pg/commitdiff/42121790ca9b27e01fd0471fdac28ec4a381eaee Andrew Dunstan pushed: - perltidy run prior to branching. ------- https://git.postgresql.org/pg/commitdiff/d8421390996dcd762383a28e57d1f3f16cc5f76f - Update typedefs list. ------- https://git.postgresql.org/pg/commitdiff/2c64d200484c40c1bfbd532bf140bea672f267a1 - pgindent run prior to branching. ------- https://git.postgresql.org/pg/commitdiff/1e9c8580904625576871eeb2efec7f04d4c3bc1c - Stamp HEAD as 12devel. Let the hacking begin ... https://git.postgresql.org/pg/commitdiff/feced1387f07c3fa6c47d36a68962750e6065486 - Use more modern instructions for creating a new dev cycle. https://git.postgresql.org/pg/commitdiff/56b4da8c9d11f685f1fe2e11cf015e850913b6b8 == Pending Patches == Tomáš Vondra sent in another revision of a patch to implement BRIN multi-range indexes. Michaël Paquier sent in another revision of a patch to rework some error messages around file handling and add an interface to read/write/fsync with transient files. Konstantin Knizhnik sent in another revision of a patch to implement libpq compression. Alexander Kuzmenkov sent in another revision of a patch to remove unneeded self-joins. David Rowley sent in a patch to generate partitioning tuple conversion maps faster. Kyotaro HORIGUCHI sent in a patch to remove dynamic_shared_memroy_type=none. Michaël Paquier sent in a patch to make advancing a slot for an unreserved slot result in an error. Kyotaro HORIGUCHI sent in another revision of a patch to restrict maximum keep segments by repslots. Kyotaro HORIGUCHI sent in another revision of a patch to protect syscache from bloating with negative cache entries. Kyotaro HORIGUCHI sent in a patch to fix a too-stringent Assert() in the btree code. Artur Zakirov sent in a patch to update the snowball stemmers. Artur Zakirov sent in another revision of a patch to implement a Nepali snowball dictionary. Magnus Hagander sent in another revision of a patch to allow enabling checksums in an instance that didn't already have them. Álvaro Herrera and David Rowley traded patches to fix get_relkind_objtype. Peter Eisentraut sent in a patch to add a server-side read-only "ssl_library" parameter. Lætitia Avrot sent in a patch to clarify the fact that CHECK constraints are not currently able to enforce business rules cross-table. Ashutosh Bapat sent in three revisions of a patch to fix a thinko/typo in ExecSimpleRelationInsert/Update. Takeshi Ideriha sent in a PoC patch to implement a global shared meta cache. Amit Langote sent in three more revisions of a patch to add partition tree inspection functions. David Rowley sent in a patch to fix run-time partition pruning for UNION ALL parents. Jerry Jelinek sent in a patch to provide an option to disable WAL recycling. Antonin Houska sent in another revision of a patch to implement at-rest encryption. Konstantin Knizhnik sent in another revision of a patch to implement WAL prefetch. Thomas Munro and Fujii Masao traded patches to speed up relation deletes during recovery. Daniel Gustafsson sent in two more revisions of a patch to implement ecure Transport SSL library on macOS as OpenSSL alternative. Andres Freund sent in a patch to allow cancelling VACUUM of nbtrees with corrupted right links. Michaël Paquier sent in two revisions of a patch to fix a bug that resulted in a PANIC during crash recovery of a recently promoted standby. Peter Eisentraut sent in a patch to ignore attempts to add TOAST table to shared or catalog tables. Justin Pryzby sent in another revision of a patch to add psql tab completion for more cases in partitioned tables. Yugo Nagata sent in a patch to forbid referencing columns by names in ALTER INDEX ... SET STATISTICS. Andrey V. Lepikhov sent in another revision of a patch to implement retail IndexTuple deletion and add a quick vacuum strategy based on it. Yugo Nagata sent in three revisions of a patch to document the EXCLUDING option to CREATE TABLE ... LIKE. Nikita Glukhov sent in another revision of a patch to implement JSON_TABLE. Nikita Glukhov sent in another revision of a patch to implement jsonpath. Nikita Glukhov sent in another revision of a patch to implement the SQL/JSON functions. Michaël Paquier sent in a patch to fail hard when facing corrupted two-phase state files and minimize the window between the history file and end-of-recovery record. Yugo Nagata sent in a patch to fix an error message when trying to alter statistics on an included column. Masahiko Sawada sent in two revisions of a patch to implement pg_copy_logical_replication_slot(). Nikita Glukhov sent in another revision of a patch to document SQL/JSON. Teodor Sigaev sent in another revision of a patch to improve cost_sort(). Michaël Paquier sent in another revision of a patch to implement WAIT_EVENT_WAL_SYNC. Amit Langote sent in a patch to make changing a slot's descriptor cheaper by pre-allocating a dedicated slot for each partition that requires it. Kyotaro HORIGUCHI sent in a patch to implement a shared-memory based stats collector, avoiding some of the performance issues with the current file-based one. Thomas Munro sent in another revision of a patch to enable parallel query with SERIALIZABLE isolation and enable the read-only SERIALIZABLE optimization for parallel query. Peter Eisentraut sent in a patch to fix an assert in nested SQL procedure calls. Nikita Glukhov sent in another revision of a patch to implement k-Nearest-Neighbor searches atop SP-GiST. Álvaro Herrera sent in a patch to fix a crash when ALTER TABLE recreates indexes on partitions. Álvaro Herrera sent in a patch to make CancelVirtualTransaction more efficient. Haribabu Kommi sent in another revision of a patch to enable pg_stat_statements_reset to reset specific query/user/db statistics. Sergei Kornilov sent in another revision of a patch to refactor the recovery.conf API. Michaël Paquier sent in another revision of a patch to extend the lookup routines for FDW and foreign server with NULL handling, refactor the routines for subscription and publication lookups, and eliminate user-visible cache lookup errors for objaddr SQL functions. Jonathan Katz sent in a patch to clarify the support for new window function capabilities added in v11.
В списке pgsql-announce по дате отправления: