Fujii Masao

to transformAggregateCall, instead of abusing fields in Aggref to carry them
temporarily.  No change in functionality but hopefully the code is a bit
clearer now.  Per gripe from Gokulakannan Somasundaram.

Also fix and uncomment an old example of creating a GIST index, and make
a couple of other minor editorial adjustments.

the master is still in recovery. We don't support cascading slaves yet.

Patch by Fujii Masao, with slightly changed wording.

correct, as described in comments at start of xlog.c

Jaime Casanova

Add ERRCODE_INVALID_PASSWORD sqlstate error code.

In particular, the assertion that shmall is sufficiently sized by default
is slowly becoming untrue.

by Dan O'Hara.

Patch by Teodor Sigaev

unable to read a stats file for reasons other than ENOENT, and having to reset
last_statrequest because it's later than current time in the collector.
Not clear if this will shed any light on the "pgstat wait timeout" business,
but it seems like a good idea in general.

In passing, do some message-style-police work on recently-added
pgstat_reset_shared_counters code.

properly; it's been making that comment uglier with each run.

This resulted in useless extra work during every call of parseRelOptions,
but no bad effects other than that.  Noted by Alvaro.

indexes, rather than printing them twice.  Per my gripe when the exclusion
constraint feature was committed.

corner cases that come up in certain timezones (apparently, only those with
lots and lots of distinct TZ transition rules, as far as I can gather from
a quick scan of their archives).  Per suggestion from Jeevan Chalke.

Back-patch to 8.4.  Possibly we need to push this into earlier releases
as well, but I'm hesitant to update them to the 64-bit tzcode without
more thought and testing.

assertion failure reported by Erik Rijkers, but this alone doesn't explain
the failure.

by joining to pg_constraint.conindid, instead of the former technique of
joining indirectly through pg_depend.  This is much more straightforward
and probably faster as well.  I had originally desisted from changing these
queries when conindid was added because I was worried about losing
performance, but if we join on conrelid as well as conindid then the index
on conrelid can be used when pg_constraint is large.

exclusion constraints.  Not sure how we managed to update the comment for
it in catalogs.sgml but miss this one.

Noted while reviewing a patch from KaiGai Kohei.

instead of an exclusive lock.

The change is almost for code cleanup. Since there seems to be no
performance benefits from it, backports should not be needed.

Fujii Masao

7.4.28.

The latter is considered unwarranted chumminess with the implementation,
and can lead to crashes with recent Perl versions.

Report and fix by Tim Bunce.  Back-patch to all versions containing the
questionable coding pattern.

Samoa, Chile; corrections to recent changes in Paraguay and Bangladesh.

ecpg now adds a unique counter to its varchar struct definitions to make these definitions unique, too. It used to use the linenumber but in the rare case of two definitions in one line this was not unique.

--single-transaction are both used and the failure happens in commit,
e.g. failed deferred trigger.  Also properly free BEGIN/COMMIT result
structures from --single-transaction.

Per report from Dominic Bevacqua

Tim Landscheidt