== PostgreSQL Weekly News - August 26 2018 ==

== PostgreSQL Weekly News - August 26 2018 ==

== PostgreSQL Product News ==

PostGIS 2.5.0rc1 the industry standard geographic information
system package for PostgreSQL, released.
http://postgis.net/2018/08/19/postgis-2.5.0rc1/

Slony 2.2.7, a trigger-based logical replication system for PostgreSQL,
released.
http://www.slony.info/

== PostgreSQL Jobs for August ==

http://archives.postgresql.org/pgsql-jobs/2018-08/

== PostgreSQL Local ==

PostgreOpen 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.
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.
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(at)fetter(dot)org(dot)

== Applied Patches ==

Michaël Paquier pushed:

- Clarify comment about assignment and reset of temp namespace ID in MyProc.
The new wording comes from Álvaro, which I modified a bit. Reported-by:
Andres Freund, Álvaro Herrera Author: Álvaro Herrera, Michael Paquier
Discussion: https://postgr.es/m/20180809165047.GK13638@paquier.xyz
Backpatch-through: 11
https://git.postgresql.org/pg/commitdiff/1339fcc896173407d6930dffbc185fe08f1ae86b

- Fix typo in description of enable_parallel_hash. Author: Kyotaro Horiguchi
Discussion:
https://postgr.es/m/20180821.115841.93250330.horiguchi.kyotaro@lab.ntt.co.jp
https://git.postgresql.org/pg/commitdiff/d8c83800c3ed2f0d677eb6620a9e9dc7b81a678b

- Fix set of NLS translation issues While monitoring the code, a couple of
issues related to string translation has showed up: - Some routines for
auto-updatable views return an error string, which sometimes missed the shot.
A comment regarding string translation is added for each routine to help with
future features. - GSSAPI authentication missed two translations. - vacuumdb
handles non-translated strings. - GetConfigOptionByNum should translate
strings. This part is not. back-patched as after a minor upgrade this could
be surprising for users. Reported-by: Kyotaro Horiguchi Author: Kyotaro
Horiguchi Reviewed-by: Michael Paquier, Tom Lane Discussion:
https://postgr.es/m/20180810.152131.31921918.horiguchi.kyotaro@lab.ntt.co.jp
Backpatch-through: 9.3
https://git.postgresql.org/pg/commitdiff/72be8c29a18812975fcc8765a122faf0e4d0c755

- Add regression tests for VACUUM and ANALYZE with relation skips. When a user
does not have ownership on a relation, then specific log messages are
generated. This new test suite adds coverage for all the possible log
messages generated, which will be useful to check the consistency of any
refactoring related to ownership checks for relations vacuumed or analyzed.
Author: Michael Paquier Reviewed-by: Nathan Bossart Discussion:
https://postgr.es/m/20180812222142.GA6097@paquier.xyz
https://git.postgresql.org/pg/commitdiff/98abc738027e866f89b0ecf6f6a30b16e000e804

- Do not dump identity sequences with excluded parent table. This commit
prevents a crash of pg_dump caused by the exclusion of a table which has
identity columns, as the table would be correctly excluded but not its
identity sequence. In order to fix that, identity sequences are excluded if
the parent table is defined as such. Knowing about such sequences has no
meaning without their parent table anyway. Reported-by: Andy Abelisto Author:
David Rowley Reviewed-by: Peter Eisentraut, Michael Paquier Discussion:
https://postgr.es/m/153479393218.1316.8472285660264976457@wrigleys.postgresql.org
Backpatch-through: 10
https://git.postgresql.org/pg/commitdiff/b965f2617184032687037547204e1db1c1e1a56c

- Add more tests for VACUUM skips with partitioned tables. A VACUUM or ANALYZE
command listing directly a partitioned table expands it to its partitions,
causing all elements of a tree to be processed with individual ownership
checks done. This results in different relation skips depending on the
ownership policy of a tree, which may not be consistent for a partition tree.
This commit adds more tests to ensure that any future refactoring allows to
keep a consistent behavior, or at least that any changes done are easily
identified and checked. The current behavior of VACUUM with partitioned
tables is present since 10. Author: Nathan Bossart Reviewed-by: Michael
Paquier Discussion:
https://postgr.es/m/DC186201-B01F-4A66-9EC4-F855A957C1F9@amazon.com
https://git.postgresql.org/pg/commitdiff/a569eea6998a26689409ff6eb5fce2c1eab0f5e1

- Fix documentation for run-time partition pruning. Since 5220bb7, not only
Append, but also MergeAppend support the operation. Author: Amit Langote
Discussion:
https://postgr.es/m/59d8eb92-4536-c44e-54e2-305b9b3d8eb7@lab.ntt.co.jp
https://git.postgresql.org/pg/commitdiff/db72302b0a846b0790ddc487c109d7c0880d4bcc

Álvaro Herrera pushed:

- Fix typo.
https://git.postgresql.org/pg/commitdiff/69c7890441d2ababf7fd71ad8d9b75fd08b015de

- fix typo.
https://git.postgresql.org/pg/commitdiff/083651da17a712f8febd05264a339a8fce310515

- Fix typo.
https://git.postgresql.org/pg/commitdiff/55a0154efdf05ccca676455f7c51965d8eaf1d76

- Return type of txid_status is text, not txid_status. Thinko in commit
857ee8e39. Discovered-by: Gianni Ciolli
https://git.postgresql.org/pg/commitdiff/d10f7741650de3199033702c3fe98a6896fd32a9

Thomas Munro pushed:

- Provide plan_cache_mode options in postgresql.conf.sample. Author: David
Rowley Discussion:
https://postgr.es/m/CAKJS1f8YkwojSTSg8YjNYCLCXzx0fR7wBR3Gf%2BrA9_52eoPZKg%40mail.gmail.com
https://git.postgresql.org/pg/commitdiff/f9fe269ca21808c1f6a3d0d23936fa4eaf2b3839

- Wrap long line in postgresql.conf.sample. Per complaint from Michael Paquier.
https://git.postgresql.org/pg/commitdiff/af63926cf577f4c30e43b7651e93e3a5eaa262e0

- Fix typos. Author: David Rowley Discussion:
https://postgr.es/m/CAKJS1f8du35u5DprpykWvgNEScxapbWYJdHq%2Bz06Wj3Y2KFPbw%40mail.gmail.com
https://git.postgresql.org/pg/commitdiff/18e586741b41713bec31effbde96ccd6da0a4361

Peter Eisentraut pushed:

- Change PROCEDURE to FUNCTION in CREATE TRIGGER syntax. Since procedures are
now a different thing from functions, change the CREATE TRIGGER and CREATE
EVENT TRIGGER syntax to use FUNCTION in the clause that specifies the
function. PROCEDURE is still accepted for compatibility. pg_dump and
ruleutils.c output is not changed yet, because that would require a change in
information_schema.sql and thus a catversion change. Reported-by: Peter
Geoghegan <pg(at)bowt(dot)ie> Reviewed-by: Jonathan S. Katz
<jonathan(dot)katz(at)excoventures(dot)com>
https://git.postgresql.org/pg/commitdiff/0a63f996e018ac508c858e87fa39cc254a5db49f

- doc: Update uses of the word "procedure". Historically, the term procedure
was used as a synonym for function in Postgres/PostgreSQL. Now we have
procedures as separate objects from functions, so we need to clean up the
documentation to not mix those terms. In particular, mentions of "trigger
procedures" are changed to "trigger functions", and access method "support
procedures" are changed to "support functions". (The latter already used
FUNCTION in the SQL syntax anyway.) Also, the terminology in the SPI chapter
has been cleaned up. A few tests, examples, and code comments are also
adjusted to be consistent with documentation changes, but not everything.
Reported-by: Peter Geoghegan <pg(at)bowt(dot)ie> Reviewed-by: Jonathan S. Katz
<jonathan(dot)katz(at)excoventures(dot)com>
https://git.postgresql.org/pg/commitdiff/b19495772e48ecd32de9a906ddf8c25e16007575

- Change PROCEDURE to FUNCTION in CREATE OPERATOR syntax. Since procedures are
now a different thing from functions, change the CREATE OPERATOR syntax to use
FUNCTION in the clause that specifies the function. PROCEDURE is still
accepted for compatibility. Reported-by: Peter Geoghegan <pg(at)bowt(dot)ie>
Reviewed-by: Jonathan S. Katz <jonathan(dot)katz(at)excoventures(dot)com>
https://git.postgresql.org/pg/commitdiff/d12782898eb5979bef3c6dd0d80b93d1aaf53cac

- doc: Clarify some wording in PL/pgSQL about transactions. Some text was still
claiming that committing transactions was not possible in PL/pgSQL.
https://git.postgresql.org/pg/commitdiff/7ceb6fb84c8cfd49c5ba92dda1c1669ba8fa687f

- PL/pgSQL: Extend test case. This test was supposed to check the interaction
of INOUT and default parameters in a procedure call, but it only checked the
case where the parameter was not supplied. Now it also checks the case where
the parameter was supplied. It was already working correctly, so no code
changes required.
https://git.postgresql.org/pg/commitdiff/d2cc897b3da9358f850dd9fa5a1a6c7ebc7bd0cf

- Copy-editing of pg_verify_checksums help and ref page. Reformat synopsis, put
options into better order, make the desciption line a bit shorter, and put
more details into the description.
https://git.postgresql.org/pg/commitdiff/2d41d914ab70cfd45f89bc1fdf682144efa001b2

- Copy-editing of pg_verify_checksums help and ref page. Reformat synopsis, put
options into better order, make the desciption line a bit shorter, and put
more details into the description.
https://git.postgresql.org/pg/commitdiff/2d41d914ab70cfd45f89bc1fdf682144efa001b2

Tom Lane pushed:

- In libpq, don't look up all the hostnames at once. Historically, we looked up
the target hostname in connectDBStart, so that PQconnectPoll did not need to
do DNS name resolution. The patches that added multiple-target-host support
to libpq preserved this division of labor; but it's really nonsensical now,
because it means that if any one of the target hosts fails to resolve in DNS,
the connection fails. That negates the no-single-point-of-failure goal of the
feature. Additionally, DNS lookups aren't exactly cheap, but the code did
them all even if the first connection attempt succeeds. Hence, rearrange so
that PQconnectPoll does the lookups, and only looks up a hostname when it's
time to try that host. This does mean that PQconnectPoll could block on a DNS
lookup --- but if you wanted to avoid that, you should be using hostaddr, as
the documentation has always specified. It seems fairly unlikely that any
applications would really care whether the lookup occurs inside PQconnectStart
or PQconnectPoll. In addition to calling out that fact explicitly, do some
other minor wordsmithing in the docs around the multiple-target-host feature.
Since this seems like a bug in the multiple-target-host feature, backpatch to
v10 where that was introduced. In the back branches, avoid moving any
existing fields of struct pg_conn, just in case any third-party code is
looking into that struct. Tom Lane, reviewed by Fabien Coelho Discussion:
https://postgr.es/m/4913.1533827102@sss.pgh.pa.us
https://git.postgresql.org/pg/commitdiff/5ca00774194dc179d02867d536b73eb85fffd227

- Suppress uninitialized-variable warning in new SCRAM code. While we generally
don't sweat too much about "may be used uninitialized" warnings from older
compilers, I noticed that there's a fair number of buildfarm animals that are
producing such a warning *only* for this variable. So it seems worth
silencing.
https://git.postgresql.org/pg/commitdiff/b0c5da615ec45bcd24b97a1d55b1f489b9830a4b

- Make syslogger more robust against failures in opening CSV log files. The
previous coding figured it'd be good enough to postpone opening the first CSV
log file until we got a message we needed to write there. This is unsafe,
though, because if the open fails we end up in infinite recursion trying to
report the failure. Instead make the CSV log file management code look as
nearly as possible like the longstanding logic for the stderr log file. In
particular, open it immediately at postmaster startup (if enabled), or when we
get a SIGHUP in which we find that log_destination has been changed to enable
CSV logging. It seems OK to fail if a postmaster-start-time open attempt
fails, as we've long done for the stderr log file. But we can't die if we
fail to open a CSV log file during SIGHUP, so we're still left with a problem.
In that case, write any output meant for the CSV log file to the stderr log
file. (This will also cover race-condition cases in which backends send CSV
log data before or after we have the CSV log file open.) This patch also fixes
an ancient oversight that, if CSV logging was turned off during a SIGHUP, we
never actually closed the last CSV log file. In passing, remember to reset
whereToSendOutput = DestNone during syslogger start, since (unlike all other
postmaster children) it's forked before the postmaster has done that. This
made for a platform-dependent difference in error reporting behavior between
the syslogger and other children: except on Windows, it'd report problems to
the original postmaster stderr as well as the normal error log file(s). It's
barely possible that that was intentional at some point; but it doesn't seem
likely to be desirable in production, and the platform dependency definitely
isn't desirable. Per report from Alexander Kukushkin. It's been like this
for a long time, so back-patch to all supported branches. Discussion:
https://postgr.es/m/CAFh8B==iLUD_gqC-dAENS0V+kVrCeGiKujtKqSQ7++S-caaChw@mail.gmail.com
https://git.postgresql.org/pg/commitdiff/bff84a547d71cd466c21f9c4625e64340aab7dd2

- Make syslogger more robust against failures in opening CSV log files. The
previous coding figured it'd be good enough to postpone opening the first CSV
log file until we got a message we needed to write there. This is unsafe,
though, because if the open fails we end up in infinite recursion trying to
report the failure. Instead make the CSV log file management code look as
nearly as possible like the longstanding logic for the stderr log file. In
particular, open it immediately at postmaster startup (if enabled), or when we
get a SIGHUP in which we find that log_destination has been changed to enable
CSV logging. It seems OK to fail if a postmaster-start-time open attempt
fails, as we've long done for the stderr log file. But we can't die if we
fail to open a CSV log file during SIGHUP, so we're still left with a problem.
In that case, write any output meant for the CSV log file to the stderr log
file. (This will also cover race-condition cases in which backends send CSV
log data before or after we have the CSV log file open.) This patch also fixes
an ancient oversight that, if CSV logging was turned off during a SIGHUP, we
never actually closed the last CSV log file. In passing, remember to reset
whereToSendOutput = DestNone during syslogger start, since (unlike all other
postmaster children) it's forked before the postmaster has done that. This
made for a platform-dependent difference in error reporting behavior between
the syslogger and other children: except on Windows, it'd report problems to
the original postmaster stderr as well as the normal error log file(s). It's
barely possible that that was intentional at some point; but it doesn't seem
likely to be desirable in production, and the platform dependency definitely
isn't desirable. Per report from Alexander Kukushkin. It's been like this
for a long time, so back-patch to all supported branches. Discussion:
https://postgr.es/m/CAFh8B==iLUD_gqC-dAENS0V+kVrCeGiKujtKqSQ7++S-caaChw@mail.gmail.com
https://git.postgresql.org/pg/commitdiff/bff84a547d71cd466c21f9c4625e64340aab7dd2

Andrew Gierth pushed:

- Reduce an unnecessary O(N^3) loop in lexer. The lexer's handling of operators
contained an O(N^3) hazard when dealing with long strings of + or -
characters; it seems hard to prevent this case from being O(N^2), but the
additional N multiplier was not needed. Backpatch all the way since this has
been there since 7.x, and it presents at least a mild hazard in that trying to
do Bind, PREPARE or EXPLAIN on a hostile query could take excessive time
(without honouring cancels or timeouts) even if the query was never executed.
https://git.postgresql.org/pg/commitdiff/d4a63f829702cf28adb5db7e2ed44d2d9d893451

- Fix lexing of standard multi-character operators in edge cases. Commits
c6b3c939b (which fixed the precedence of >=, <=, <> operators) and 865f14a2d
(which added support for the standard => notation for named arguments) created
a class of lexer tokens which look like multi-character operators but which
have their own token IDs distinct from Op. However, longest-match rules meant
that following any of these tokens with another operator character, as in
(1<>-1), would cause them to be incorrectly returned as Op. The error here
isn't immediately obvious, because the parser would usually still find the
correct operator via the Op token, but there were more subtle problems: 1. If
immediately followed by a comment or +-, >= <= <> would be given the old
precedence of Op rather than the correct new precedence; 2. If followed by a
comment, != would be returned as Op rather than as NOT_EQUAL, causing it not
to be found at all; 3. If followed by a comment or +-, the => token for named
arguments would be lexed as Op, causing the argument to be mis-parsed as a
simple expression, usually causing an error. Fix by explicitly checking for
the operators in the {operator} code block in addition to all the existing
special cases there. Backpatch to 9.5 where the problem was introduced.
Analysis and patch by me; review by Tom Lane. Discussion:
https://postgr.es/m/87va851ppl.fsf@news-spur.riddles.org.uk
https://git.postgresql.org/pg/commitdiff/a40631a920accbcca1a49a909d380308d95b4674

Andres Freund pushed:

- Deduplicate code between slot_getallattrs() and slot_getsomeattrs(). Code in
slot_getallattrs() is the same as if slot_getsomeattrs() is called with number
of attributes specified in the tuple descriptor. Implement it that way instead
of duplicating the code between those two functions. This is part of a
patchseries abstracting TupleTableSlots so they can store arbitrary forms of
tuples, but is a nice enough cleanup on its own. Author: Ashutosh Bapat
Reviewed-By: Andres Freund Discussion:
https://postgr.es/m/20180220224318.gw4oe5jadhpmcdnm@alap3.anarazel.de
https://git.postgresql.org/pg/commitdiff/88ebd62fcc2ea7c55c0858f6dd4800d51383529f

- Introduce minimal C99 usage to verify compiler support. This just converts a
few for loops in postgres.c to declare variables in the loop initializer, and
uses designated initializers in smgr.c's definition of smgr callbacks.
Author: Andres Freund Discussion:
https://postgr.es/m/97d4b165-192d-3605-749c-f614a0c4e783@2ndquadrant.com
https://git.postgresql.org/pg/commitdiff/143290efd0795b61ed2c8358fc1767e799140047

- Require C99 (and thus MSCV 2013 upwards). In 86d78ef50e01 I enabled configure
to check for C99 support, with the goal of checking which platforms support
C99. While there are a few machines without C99 support among our buildfarm
animals, de-supporting them for v12 was deemed acceptable. While not tested
in aforementioned commit, the biggest increase in minimum compiler version
comes from MSVC, which gained C99 support fairly late. The subset in MSVC 2013
is sufficient for our needs, at this point. While that is a significant
increase in minimum version, the existing windows binaries are already built
with a new enough version. Make configure error out if C99 support could not
be detected. For MSVC builds, increase the minimum version to 2013. The
increase to MSVC 2013 allows us to get rid of VCBuildProject.pm, as that was
only required for MSVC 2005/2008. Author: Andres Freund Discussion:
https://postgr.es/m/97d4b165-192d-3605-749c-f614a0c4e783@2ndquadrant.com
https://git.postgresql.org/pg/commitdiff/d9dd406fe281d22d5238d3c26a7182543c711e74

- LLVMJIT: LLVMGetHostCPUFeatures now is upstream, use LLMV version if
available. Noticed thanks to buildfarm animal seawasp. Author: Andres Freund
Backpatch: v11-, where LLVM based JIT compliation was introduced.
https://git.postgresql.org/pg/commitdiff/cb92520563834577d3afbbedcc0df4ee0aac3445

- Remove test for VA_ARGS, implied by C99. This simplifies logic / reduces
duplication in a few headers. Author: Andres Freund Discussion:
https://postgr.es/m/97d4b165-192d-3605-749c-f614a0c4e783@2ndquadrant.com
https://git.postgresql.org/pg/commitdiff/8ecdefc261abbd35d6280cdd8fd749e83c3fd199

- Remove test for VA_ARGS, implied by C99. This simplifies logic / reduces
duplication in a few headers. Author: Andres Freund Discussion:
https://postgr.es/m/97d4b165-192d-3605-749c-f614a0c4e783@2ndquadrant.com
https://git.postgresql.org/pg/commitdiff/8ecdefc261abbd35d6280cdd8fd749e83c3fd199

Bruce Momjian pushed:

- docs: clarify plpython SD and GD dictionary behavior. Reported-by: Adam
Bielański Discussion:
https://postgr.es/m/153484305538.1370.7605856225879294548@wrigleys.postgresql.org
Backpatch-through: 9.3
https://git.postgresql.org/pg/commitdiff/a6ca9c2a1bd0d57e8f359504e91ee0208f65ed58

- docs: Clarify pg_ctl initdb option text to match options proto. The options
string appeared in PG 10. Reported-by: pgsql-kr(at)postgresql(dot)kr Discussion:
https://postgr.es/m/153500377658.1378.6587007319641704057@wrigleys.postgresql.org
Backpatch-through: 10
https://git.postgresql.org/pg/commitdiff/7abf8ee1e841684cd51472a7476b3f6b9441e70f

- doc: add doc link for 'applicable_roles'. Reported-by: Ashutosh Sharma
Discussion:
https://postgr.es/m/CAE9k0PnhnL6MNDLuvkk8USzOa_DpzDzFQPAM_uaGuXbh9HMKYw@mail.gmail.com
Author: Ashutosh Sharma Backpatch-through: 9.3
https://git.postgresql.org/pg/commitdiff/dcb2efdbdd8fe46be35069ea58acebbc4ff2723a

- doc: "Latest checkpoint location" will not match in pg_upgrade. Mention that
"Latest checkpoint location" will not match in pg_upgrade if the standby
server is still running during the upgrade, which is possible. "Match" text
first appeared in PG 9.5. Reported-by: Paul Bonaud Discussion:
https://postgr.es/m/c7268794-edb4-1772-3bfd-04c54585c24e@trainline.com
Backpatch-through: 9.5
https://git.postgresql.org/pg/commitdiff/cc2e457fe8a3f685b4f9b9dce05b0c027b39459f

Jeff Davis pushed

- Comment fix for rewriteheap.h. The description of the filename for mapping
files did not match the code.
https://git.postgresql.org/pg/commitdiff/e75733d46c8444c0f5c9578bdf576b29039aac1f

- Change extension of spilled ReorderBufferChange data to ".tmp". The previous
extension, ".snap", was chosen for historical reasons and became confusing.
Discussion:
https://postgr.es/m/CAMp0ubd_P8vBGx8=MfDXQJZxHA5D_Zarw5cCkDxJ_63+pWRJ9w@mail.gmail.com
https://git.postgresql.org/pg/commitdiff/91f26d5fe47e3b06e878f2f1949cbd35e9576c16

- Reconsider new file extension in commit 91f26d5f. Andres and Tom objected to
the choice of the ".tmp" extension. Changing to Andres's suggestion of
".spill". Discussion:
https://postgr.es/m/88092095-3348-49D8-8746-EB574B1D30EA%40anarazel.de
https://git.postgresql.org/pg/commitdiff/ba9d35b8eb8466cf445c732a2e15ca5790cbc6c6

== Pending Patches ==

Tom Lane sent in a patch to turn useful_strerror() into a globally available
wrapper pg_strerror() that replaces strerror() everyplace, implements %m in
snprintf.c and causes it to be used all the time.

Tom Lane sent in another revision of a patch to speed up src/port/snprintf.c.

David Rowley sent in a patch to calculate total_table_pages after
set_base_rel_sizes.

Amit Langote sent in another revision of a patch to allocate dedicated slots of
partition tuple conversion.

Konstantin Knizhnik sent in another revision of a patch to add flexible
compression to libpq.

Amit Khandekar sent in two more revisions of a patch to slot-ify partition tuple
conversion.

Peter Eisentraut sent in a patch to factor out the CREATE INDEX CONCURRENTLY
code that waits for transactions with older snapshots to finish into a new
function WaitForOlderSnapshots().

Peter Eisentraut sent in a patch to ignore attempts to add TOAST table to shared
or catalog tables.

Chris Travers sent in a patch to add options INSERTMETHOD=[insert|copy] and
TWOPHASECOMMIT=[off|on] to the PostgreSQL FDW.

Nikita Glukhov sent in another revision of a patch to implement JSONPATH.

David Rowley and Amit Langote traded patches to speed up INSERTs and UPDATEs on
partitioned tables.

Daniel Vérité sent in another revision of a patch to implement a CSV output
format option for psql.

Surafel Temesgen sent in another revision of a patch to add conflict handling to
COPY FROM.

Peter Eisentraut sent in a patch to fix a snapshot leak warning for some
procedures.

David Rowley sent in a patch to make the executor's range table more efficient
by changing it from a List to an array.

Ashutosh Bapat sent in two more revisions of a patch to create a TableTupleslot
abstraction.

Tom Lane sent in another revision of a patch to improve OR conditions on joined
columns, a common star schema problem.

Haribabu Kommi sent in a patch to change the FDW RefetchForeignRow API to use
TupleTableSlot along with supporting changes to "make check-world."

Haribabu Kommi sent in two more revisions of a patch to fix some of the
isolation tests.

Tsutomu Yamada sent in three more revisions of a patch to fix the --help options
in contrib/oid2name and vacuumlo.

Tsutomu Yamada sent in another revision of a patch to add a progress monitor for
CLUSTER.

Yugo Nagata sent in a patch to refactor textToQualifiedNameList() to be a thin
wrapper around stringToQualifiedNameList() rather than a separate implementation
of essentially the same functionality.

Etsuro Fujita sent in another revision of a patch to disable support for
partitionwise joins in problematic cases.

Kyotaro HORIGUCHI sent in a patch to fix a bug in the way the PostgreSQL FDW
performed UPDATEs, wrongly using CTIDs as the criterion for identity.

Alexandra Ryzhevich sent in two more revisions of a patch to add regression
tests for the default monitoring roles.

Konstantin Knizhnik sent in another revision of a patch to implement
auto-prepare.

Jim Finnerty sent in another revision of a patch to have the planner drop
redundant DISTINCT columns in cases where it can show that's what they are.

Peter Eisentraut sent in a patch to add some not null constraints to some of the
pg_catalog tables.

Michaël Paquier and Nathan Bossart traded patches to improve VACUUM and ANALYZE
by avoiding an early lock queue.

Fabien COELHO sent in two revisions of a patch to fix some
host/hostaddr/conninfo inconsistencies in libpq.

Noriyoshi Shinoda sent in another revision of a patch to make it possible to set
work_mem via the PostgreSQL FDW.

Yugo Nagata sent in another revision of a patch to fix an issue where
has_table_privilege for a table in unprivileged schema causes an error.

Noah Misch sent in a patch to ensure that wal_sender_timeout ignores server-side
latency.

David Rowley sent in a patch to remove some duplicate words in the comments in
src/backend/partitioning/partprune.c and src/backend/statistics/dependencies.c.

Bradley DeJong sent in a patch to add a note to protocol.sgml regarding
CopyData.