== PostgreSQL Weekly News - June 18 2017 ==

From: David Fetter <david(at)fetter(dot)org>
To: PostgreSQL Announce <pgsql-announce(at)postgresql(dot)org>
Subject: == PostgreSQL Weekly News - June 18 2017 ==
Date: 2017-06-18 21:25:38
Message-ID: 20170618212538.GA13300@fetter.org
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-announce

== PostgreSQL Weekly News - June 18 2017 ==

PGConf.Brazil 2017 OnLine Edition will be live from Brazil on July 10-14 2017.

== PostgreSQL Jobs for June ==


== PostgreSQL Local ==

Postgres Vision will take place in Boston, June 26 - 28, 2017.

Swiss PGDay in Rapperswil will take place June 30, 2017.
The schedule is online and registration is open.

PGBR2017 will take place in Porto Alegre, Rio Grande do Sul,
Brazil on September 14-16 2017. The CfP is open until June 30, 2017.

PostgresOpen will occur September 6-8, 2017 in San Francisco.

PGDay UK 2017 will take place July 4, 2017 in London, England, UK.

PGDay Austin 2017 will be held on Saturday, August 26 2017.

PostgreSQL Conference Europe 2017 will be held on October 24-27, 2017 in the
Warsaw Marriott Hotel, in Warsaw, Poland.

PGConf.ASIA 2017 will take place on December 4-6 2017 in Akihabara, Tokyo,
Japan. The CfP is open until July 31, 2017. Send submissions to
pgconf-asia-2017-submission AT pgconf DOT asia

== 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 Pacific time.
Please send English language ones to david(at)fetter(dot)org, German language
to pwn(at)pgug(dot)de, Italian language to pwn(at)itpug(dot)org(dot)

== Applied Patches ==

Tatsuo Ishii pushed:

- Fix ALTER TABLE doc examples. Patch by Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>.
Confirmed by Amit Langote, who is the original author of the document part.

- Fix typo in PostgreSQL 10.0 release note. Patch by Yugo Nagata.

- Fix document bug regarding read only transactions. It was explained that read
only transactions (not in standby) allow to update sequences. This had been
wrong since the commit: 05d8a561ff85db1545f5768fe8d8dc9d99ad2ef7 Discussion:

Peter Eisentraut pushed:

- Stop table sync workers when subscription relation entry is removed. When a
table sync worker is in waiting state and the subscription table entry is
removed because of a concurrent subscription refresh, the worker could be left
orphaned. To avoid that, explicitly stop the worker when the
pg_subscription_rel entry is removed. Reported-by: Masahiko Sawada

- Stop table sync workers when subscription relation entry is removed. When a
table sync worker is in waiting state and the subscription table entry is
removed because of a concurrent subscription refresh, the worker could be left
orphaned. To avoid that, explicitly stop the worker when the
pg_subscription_rel entry is removed. Reported-by: Masahiko Sawada

- Trim trailing whitespace.

- Fix build of ICU support in Windows. and also any platform that does not have
locale_t but enabled ICU. Author: Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>

- Add MSVC build system support for ICU. Author: Ashutosh Sharma
<ashu(dot)coek88(at)gmail(dot)com> Reviewed-by: Michael Paquier

- Remove "synchronized table states" notice message. It appears to be more
confusing than useful. Reported-by: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>

- Add ICU_CFLAGS to global CPPFLAGS. The original code only added ICU_CFLAGS to
the backend build. But it is also needed for building external modules that
include pg_locale.h. So add it to the global CPPFLAGS. (This is only
relevant if ICU is not in a compiler default path, so it apparently hasn't
bitten many.)

- doc: Update information_schema documentation for identity columns. This was
apparently forgotten in the original patch.

- doc: Update external PL list. Add PL/Lua, PL/v8. Remove stale/unmaintained
PL/PHP, PL/Py, PL/Ruby, PL/Scheme. Reported-by: Adam Sah <asah(at)midgard(dot)net>

- pg_dump: Fix harmless type mixup.

- Prevent copying default collation. This will not have the desired effect and
might lead to crashes when the copied collation is used. Reported-by: Tom
Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>

- pg_dump: Allow dumping default collation. This will not work on restore, but
it will allow dumping out pg_catalog for research and documentation.
Reported-by: Neil Anderson <neil(dot)t(dot)anderson(at)gmail(dot)com> Bug: #14701

- Use correct ICU path for Windows 32 vs. 64 bit. Author: Ashutosh Sharma

- Improve code comments. Author: Erik Rijkers <er(at)xs4all(dot)nl>

- Fix typo. Author: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>

- Fix collprovider of predefined collations. An earlier version of the patch
had collprovider as an integer and thus set these to 0, but the correct
setting is now null.

- doc: Fix typo. Author: Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com>

- libpq: Message style improvements.

- psql: Use more consistent capitalization of some output headings.

- doc: Update example version numbers in pg_upgrade documentation. The exact
numbers don't matter, since they are examples, but it was looking quite dated.
For the target version, we now automatically substitute the current major
version. The updated example source version should be good for a couple of

- Put documentation of options and commands in more alphabetical order.

- doc: Whitespace fixes in man pages.

- Add missing serial comma.

- Use DEFACLOBJ_ macros in error message instead of hardcoding.

- Remove unnecessary IPC::Run inclusion. This is no longer needed because the
tests use PostgresNode. Reported-by: Michael Paquier

- Fix typo in code comment. Author: Daniel Gustafsson <daniel(at)yesql(dot)se>

- psql: Improve display of "for all tables" publications. Show "All tables"
property in \dRp and \dRp+. Don't list tables for such publications in \dRp+,
since it's redundant and the list could be very long. Author: Masahiko Sawada
<sawada(dot)mshk(at)gmail(dot)com> Author: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>

- doc: Add section about logical replication restrictions.

- Fix ICU collation use on Windows. Windows uses a separate code path for libc
locales. The code previously ended up there also if an ICU collation should
be used, leading to a crash. Reported-by: Ashutosh Sharma

- Use RangeVarGetRelidExtended() in AlterSequence(). This allows us to combine
the opening and the ownership check. Reported-by: Robert Haas

- doc: Add note that COPY commands are published as INSERTs.

- Define HAVE_UCOL_STRCOLLUTF8 on Windows. This should normally be determined
by a configure check, but until someone figures out how to do that on Windows,
it's better that the code uses the new function by default.

- Set statement timestamp in apply worker. This ensures that triggers can see
an up-to-date timestamp. Reported-by: Konstantin Evteev <konst583(at)gmail(dot)com>

- doc: Fix typo. Author: Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com>

- doc: Fix typo. Author: Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com>

- Documentation spell checking and markup improvements.

Tom Lane pushed:

- Fix ALTER SEQUENCE OWNED BY to not rewrite the sequence relation. It's not
necessary for it to do that, since OWNED BY requires only ordinary catalog
updates and doesn't affect future sequence values. And pg_upgrade needs to
use OWNED BY without having it change the sequence's relfilenode. Commit
3d79013b9 broke this by making all forms of ALTER SEQUENCE change the
relfilenode; that seems to be the explanation for the hard-to-reproduce
buildfarm failures we've been seeing since then. Discussion:

- Assert that we don't invent relfilenodes or type OIDs in binary upgrade.
During pg_upgrade's restore run, all relfilenode choices should be overridden
by commands in the dump script. If we ever find ourselves choosing a
relfilenode in the ordinary way, someone blew it. Likewise for pg_type OIDs.
Since pg_upgrade might well succeed anyway, if there happens not to be a
conflict during the regression test run, we need assertions here to keep us on
the straight and narrow. We might someday be able to remove the assertion in
GetNewRelFileNode, if pg_upgrade is rewritten to remove its assumption that
old and new relfilenodes always match. But it's hard to see how to get rid of
the pg_type OID constraint, since those OIDs are embedded in user tables in
some cases. Back-patch as far as 9.5, because of the risk of back-patches
breaking something here even if it works in HEAD. I'd prefer to go back
further, but 9.4 fails both assertions due to get_rel_infos()'s use of a
temporary table. We can't use the later-branch solution of a CTE for
compatibility reasons (cf commit 5d16332e9), and it doesn't seem worth
inventing some other way to do the query. (I did check, by dint of changing
the Asserts to elog(WARNING), that there are no other cases of unwanted OID
assignments during 9.4's regression test run.) Discussion:

- Fix confusion about number of subplans in partitioned INSERT setup.
ExecInitModifyTable() thought there was a plan per partition, but no, there's
only one. The problem had escaped detection so far because there would only
be visible misbehavior if there were a SubPlan (not an InitPlan) in the quals
being duplicated for each partition. However, valgrind detected a bogus
memory access in test cases added by commit 4f7a95be2, and investigation of
that led to discovery of the bug. The additional test case added here crashes
without the patch. Patch by Amit Langote, test case by me. Discussion:

- In initdb, defend against assignment of NULL values to not-null columns.
Previously, you could write _null_ in a BKI DATA line for a column that's
supposed to be NOT NULL and initdb would let it pass, probably breaking
subsequent accesses to the row. No doubt the original coding overlooked this
simple sanity check because in the beginning we didn't have any way to mark
catalog columns NOT NULL at initdb time.

- Re-run pgindent. This is just to have a clean base state for testing of Piotr
Stefaniak's latest version of FreeBSD indent. I fixed up a couple of places
where pgindent would have changed format not-nicely. perltidy not included.

- Disallow set-returning functions inside CASE or COALESCE. When we
reimplemented SRFs in commit 69f4b9c85, our initial choice was to allow the
behavior to vary from historical practice in cases where a SRF call appeared
within a conditional-execution construct (currently, only CASE or COALESCE).
But that was controversial to begin with, and subsequent discussion has
resulted in a consensus that it's better to throw an error instead of
executing the query differently from before, so long as we can provide a
reasonably clear error message and a way to rewrite the query. Hence, add a
parser mechanism to allow detection of such cases during parse analysis. The
mechanism just requires storing, in the ParseState, a pointer to the
set-returning FuncExpr or OpExpr most recently emitted by parse analysis.
Then the parsing functions for CASE and COALESCE can detect the presence of a
SRF in their arguments by noting whether this pointer changes while analyzing
their arguments. Furthermore, if it does, it provides a suitable error cursor
location for the complaint. (This means that if there's more than one SRF in
the arguments, the error will point at the last one to be analyzed not the
first. While connoisseurs of parsing behavior might find that odd, it's
unlikely the average user would ever notice.) While at it, we can also provide
more specific error messages than before about some pre-existing restrictions,
such as no-SRFs-within-aggregates. Also, reject at parse time cases where a
NULLIF or IS DISTINCT FROM construct would need to return a set. We've never
supported that, but the restriction is depended on in more subtle ways now, so
it seems wise to detect it at the start. Also, provide some documentation
about how to rewrite a SRF-within-CASE query using a custom wrapper SRF. It
turns out that the information_schema.user_mapping_options view contained an
instance of exactly the behavior we're now forbidding; but rewriting it makes
it more clear and safer too. initdb forced because of user_mapping_options
change. Patch by me, with error message suggestions from Alvaro Herrera and
Andres Freund, pursuant to a complaint from Regina Obe. Discussion:

- Fix violations of CatalogTupleInsert/Update/Delete abstraction. In commits
2f5c9d9c9 and ab0289651 we invented an abstraction layer to insulate catalog
manipulations from direct heap update calls. But evidently some patches that
hadn't landed in-tree at that point didn't get the memo completely. Fix a
couple of direct calls to simple_heap_delete to use CatalogTupleDelete
instead; these appear to have been added in commits 7c4f52409 and 7b504eb28.
This change is purely cosmetic ATM, but there's no point in having an
abstraction layer if we allow random code to break it. Masahiko Sawada and
Tom Lane Discussion:

- Fix no-longer-valid shortcuts in expression_returns_set().
expression_returns_set() used to short-circuit its recursion upon seeing
certain node types, such as DistinctExpr, that it knew the executor did not
support set-valued arguments for. That was never inherent, though, just a
reflection of laziness in execQual.c. With the new implementation of SRFs
there is no reason to think that any scalar-valued expression node could not
have a set-valued subexpression, except for AggRefs and WindowFuncs where we
know there is a parser check rejecting it. And indeed, the shortcut causes
unexpected failures for cases such as a SRF underneath DistinctExpr, because
the planner stops looking for SRFs too soon. Discussion:

- Improve release note text about set-returning-function changes. Paul Ramsey
griped about this awhile ago, but I'd been holding fire on changing it until
we settled what to do about the CASE/COALESCE issue. Discussion:

- Fix low-probability leaks of PGresult objects in the backend. We had three
occurrences of essentially the same coding pattern wherein we tried to
retrieve a query result from a libpq connection without blocking. In the case
where PQconsumeInput failed (typically indicating a lost connection), all
three loops simply gave up and returned, forgetting to clear any
previously-collected PGresult object. Since those are malloc'd not palloc'd,
the oversight results in a process-lifespan memory leak. One instance, in
libpqwalreceiver, is of little significance because the walreceiver process
would just quit anyway if its connection fails. But we might as well fix it.
The other two instances, in postgres_fdw, are somewhat more worrisome because
at least in principle the scenario could be repeated, allowing the amount of
memory leaked to build up to something worth worrying about. Moreover, in
these cases the loops contain CHECK_FOR_INTERRUPTS calls, as well as other
calls that could potentially elog(ERROR), providing another way to exit
without having cleared the PGresult. Here we need to add PG_TRY logic similar
to what exists in quite a few other places in postgres_fdw. Coverity noted
the libpqwalreceiver bug; I found the other two cases by checking all calls of
PQconsumeInput. Back-patch to all supported versions as appropriate (9.2
lacks postgres_fdw, so this is really quite unexciting for that branch).
Discussion: https://postgr.es/m/22620.1497486981@sss.pgh.pa.us

- Make configure check for IPC::Run when --enable-tap-tests is specified. The
TAP tests mostly don't work without IPC::Run, and the reason for the failure
is not immediately obvious from the error messages you get. So teach
configure to reject --enable-tap-tests unless IPC::Run exists. Mostly this
just involves adding ax_prog_perl_modules.m4 from the GNU autoconf archives.
This was discussed last year, but we held off on the theory that we might be
switching to CMake soon. That's evidently not happening for v10, so let's
absorb this now. Eugene Kazakov and Michael Paquier Discussion:
https://postgr.es/m/56BDDC20.9020506@postgrespro.ru Discussion:

- Teach pgindent to skip files generated by bison or flex automatically. If a
.c or .h file corresponds to a .y or .l file, skip indenting it. There's no
point in reindenting derived files, and these files tend to confuse pgindent.
(Which probably indicates a bug in BSD indent, but I can't get excited about
trying to fix it.) For the same reasons, add src/backend/utils/fmgrtab.c to
the set of files excluded by src/tools/pgindent/exclude_file_patterns. The
point of doing this is that it makes it safe to run pgindent over the tree
without doing "make maintainer-clean" first. While these are not the only
derived .c/.h files in the tree, they are the only ones pgindent fails on.
Removing that prerequisite step results in one less way to mess up a pgindent
run, and it's necessary if we ever hope to get to the ease of running pgindent
via "make indent".

Robert Haas pushed:

- Fix failure to remove dependencies when a partition is detached. Otherwise,
dropping the partitioned table will automatically drop any previously-detached
children, which would be unfortunate. Ashutosh Bapat and Rahila Syed,
reviewed by Amit Langote and by me. Discussion:

- Always initialize PartitionBoundInfoData's null_index. This doesn't actually
matter at present, because the current code never consults null_index for
range partitions. However, leaving it uninitialized is still a bad idea, so
let's not do that. Amul Sul, reviewed by Ashutosh Bapat Discussion:

- Teach predtest.c about CHECK clauses to fix partitioning bugs. In a CHECK
clause, a null result means true, whereas in a WHERE clause it means false.
predtest.c provided different functions depending on which set of semantics
applied to the predicate being proved, but had no option to control what a
null meant in the clauses provided as axioms. Add one. Use that in the
partitioning code when figuring out whether the validation scan on a new
partition can be skipped. Rip out the old logic that attempted (not very
successfully) to compensate for the absence of the necessary support in
predtest.c. Ashutosh Bapat and Robert Haas, reviewed by Amit Langote and
incorporating feedback from Tom Lane. Discussion:

- Fix problems related to RangeTblEntry members enrname and enrtuples. Commit
18ce3a4ab22d2984f8540ab480979c851dae5338 failed to update the comments in
parsenodes.h for the new members, and made only incomplete updates to
src/backend/nodes Thomas Munro, per a report from Noah Misch. Discussion:

Dean Rasheed pushed:

- Teach relation_is_updatable() about partitioned tables. Table partitioning,
introduced in commit f0e44751d7, added a new relkind -
RELKIND_PARTITIONED_TABLE. Update relation_is_updatable() to handle it.
Specifically, partitioned tables and simple views built on top of them are
updatable. This affects the SQL-callable functions pg_relation_is_updatable()
and pg_column_is_updatable(), and the views information_schema.views and
information_schema.columns. Dean Rasheed, reviewed by Ashutosh Bapat.

- Teach RemoveRoleFromObjectPolicy() about partitioned tables. Table
partitioning, introduced in commit f0e44751d7, added a new relkind -
RELKIND_PARTITIONED_TABLE. Update RemoveRoleFromObjectPolicy() to handle it,
otherwise DROP OWNED BY will fail if the role has any RLS policies referring
to partitioned tables. Dean Rasheed, reviewed by Amit Langote. Discussion:

- Teach PL/pgSQL about partitioned tables. Table partitioning, introduced in
commit f0e44751d7, added a new relkind - RELKIND_PARTITIONED_TABLE. Update a
couple of places in PL/pgSQL to handle it. Specifically
plpgsql_parse_cwordtype() and build_row_from_class() needed updating in order
to make table%ROWTYPE and table.col%TYPE work for partitioned tables. Dean
Rasheed, reviewed by Amit Langote. Discussion:

Álvaro Herrera pushed:

- Avoid bogus TwoPhaseState locking sequences. The optimized code in
728bd991c3c4 contains a few invalid locking sequences. To wit, the original
code would try to acquire an lwlock that it already holds. Avoid this by
moving lock acquisitions to higher-level code, and install appropriate
assertions in low-level that the correct mode is held. Authors: Michael
Paquier, Álvaro Herrera Reported-By: chuanting wang Bug: #14680 Discussion:

- Rename function for consistency. Avoid using prefix "staext" when everything
else uses "statext". Author: Kyotaro HORIGUCHI Discussion:

Andres Freund pushed:

- Don't force-assign transaction id when exporting a snapshot. Previously we
required every exported transaction to have an xid assigned. That was used to
check that the exporting transaction is still running, which in turn is needed
to guarantee that that necessary rows haven't been removed in between
exporting and importing the snapshot. The exported xid caused unnecessary
problems with logical decoding, because slot creation has to wait for all
concurrent xid to finish, which in turn serializes concurrent slot creation.
It also prohibited snapshots to be exported on hot-standby replicas. Instead
export the virtual transactionid, which avoids the unnecessary serialization
and the inability to export snapshots on standbys. This changes the file name
of the exported snapshot, but since we never documented what that one means,
that seems ok. Author: Petr Jelinek, slightly editorialized by me
Reviewed-By: Andres Freund Discussion:

Bruce Momjian pushed:

- docs: Fix pg_upgrade standby server upgrade docs. It was unsafe to instruct
users to start/stop the server after pg_upgrade was run but before the standby
servers were rsync'ed. The new instructions avoid this. RELEASE NOTES: This
fix should be mentioned in the minor release notes. Reported-by: Dmitriy
Sarafannikov and Sergey Burladyan Discussion:
https://postgr.es/m/87wp8o506b.fsf@seb.koffice.internal Backpatch-through:
9.5, where standby server upgrade instructions first appeared

- doc: remove mention of Windows junction points by pg_upgrade. pg_upgrade
never used Windows junction points but instead always used Windows hard links.
Reported-by: Adrian Klaver Discussion:
Backpatch-through: 9.3, where the mention first appeared

Noah Misch pushed:

- Reconcile nodes/*funcs.c with PostgreSQL 10 work. The _equalTableFunc()
omission of coltypmods has semantic significance, but I did not track down
resulting user-visible bugs, if any. The other changes are cosmetic only,
affecting order. catversion bump due to readfuncs.c field order change.

Heikki Linnakangas pushed:

- Fix dependency, when changing a function's argument/return type. When a new
base type is created using the old-style procedure of first creating the
input/output functions with "opaque" in place of the base type, the "opaque"
argument/return type is changed to the final base type, on CREATE TYPE.
However, we did not create a pg_depend record when doing that, so the
functions were left not depending on the type. Fixes bug #14706, reported by
Karen Huddleston. Discussion:

Magnus Hagander pushed:

- Fix typos in comments. Author: Daniel Gustafsson <daniel(at)yesql(dot)se>

- Remove incorrect comment. Author: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>

- Fix copy/paste error in docs. Author: Julien Rouhaud

== Pending Patches ==

Jeevan Ladhe sent in two more revisions of a patch to add support for a default
declarative partition.

Thomas Munro sent in another revision of a patch to ensure that there are two
transition table tuplestores for the ON CONFLICT DO UPDATE case, one for updated
tuples, and the other for inserted tuples.

Haribabu Kommi sent in another revision of a patch to put in the infrastructure
for pluggable storage.

Tom Lane sent in a patch to check that pg_upgrade never generates a new
pg_type OID and ensures that relfilenodes are all assigned.

Amit Langote sent in a patch to teach pgrowlocks to check relkind before

Jeevan Ladhe sent in a patch to fix possible optimizations in

Michaël Paquier sent in a patch to ensure that pg_receivewal and messages are
printed only in verbose mode.

Masahiko Sawada sent in a patch to make RemoveSubscriptionRel use
CatalogTupleDelete() rather than the curren simple_heap_delete.

Masahiko Sawada sent in a patch to disallow ALTER SUBSCRIPTION SET PUBLICATION
transaction block.

Bruce Momjian sent in two revisions of a patch to clarify the documentation
around hint bits as it relates to pg_upgrade.

Peter Eisentraut sent in a patch to fix the output of char node fields.

Christian Ullrich sent in a patch to make setlocale() aware of multithreading to
avoid crash.

Etsuro Fujita sent in a patch to update comments in nodeModifyTable.c.

Mithun Cy sent in another revision of a patch to implement auto_prewarm.

Beena Emerson sent in another revision of a patch to implement default
partitions for range partitions.

Surafel Temesgen sent in another revision of a patch to disallow multiple
queries per PQexec().

Marina Polyakova sent in a patch to improve pgbench by removing serialization
and deadlock errors, setting the correct default transaction isolation level,
reporting per-statement serialization and deadlock failures, and fixing the

Etsuro Fujita sent in a patch to add a missing comment for

Justin Pryzby sent in a patch to make showusage() get memory fields from

Amit Khandekar sent in another revision of a patch to make UPDATEs on
declaratively partitioned tables which change the partition key to actually move
the affected rows to the appropriate partitions.

Fabien COELHO sent in another revision of a patch to add TAP tests for pgbench.

Jeff Janes sent in another revision of a patch to prevent subscription workers
from signalling the WAL writer too much.

Peter Eisentraut sent in a WIP patch to tweak publication fetching in psql.

QL Zhuo sent in two revisions of a patch to ensure that filepath/filename are
not downcased while loading libraries.

Fabien COELHO sent in another revision of a patch to implement \gdesc in psql.

Ashutosh Sharma sent in three more revisions of a patch to fix ICU on Windows.

Etsuro Fujita sent in another revision of a patch to adjust inherited update

Konstantin Knizhnik sent in a patch to implement AES encryption in the backend.

Fabien COELHO sent in another revision of a patch to add a special variable to
psql to reflect the last query status.

Shubham Barai sent in two revisions of a patch to implement predicate locking in
GiST indexes.

Mark Rofail sent in a patch to add a record to pg_proc
(src/include/catalog/pg_proc.h), modify opr_sanity regression check expected
results to account for it, implement a low-level function called
`array_contains_elem` as an equivalent to `array_contain_compare` but accepts
anyelement instead of anyarray as the right operand.

Julien Rouhaud sent in a patch to fix a typo in insert.sgml.

Browse pgsql-announce by date

  From Date Subject
Next Message Chapman Flack 2017-06-20 12:27:50 PL/Java 1.5.1-BETA1 announced; security note.
Previous Message David Fetter 2017-06-12 05:20:13 == PostgreSQL Weekly News - June 11 2017 ==