[COMMITTERS] pgsql: Teach libpq to decode server version correctly from future serve

2016-08-05 Thread Tom Lane
Teach libpq to decode server version correctly from future servers. Beginning with the next development cycle, PG servers will report two-part not three-part version numbers. Fix libpq so that it will compute the correct numeric representation of such server versions for reporting by PQserverVers

[COMMITTERS] pgsql: Teach libpq to decode server version correctly from future serve

2016-08-05 Thread Tom Lane
Teach libpq to decode server version correctly from future servers. Beginning with the next development cycle, PG servers will report two-part not three-part version numbers. Fix libpq so that it will compute the correct numeric representation of such server versions for reporting by PQserverVers

[COMMITTERS] pgsql: Teach libpq to decode server version correctly from future serve

2016-08-05 Thread Tom Lane
Teach libpq to decode server version correctly from future servers. Beginning with the next development cycle, PG servers will report two-part not three-part version numbers. Fix libpq so that it will compute the correct numeric representation of such server versions for reporting by PQserverVers

[COMMITTERS] pgsql: Teach libpq to decode server version correctly from future serve

2016-08-05 Thread Tom Lane
Teach libpq to decode server version correctly from future servers. Beginning with the next development cycle, PG servers will report two-part not three-part version numbers. Fix libpq so that it will compute the correct numeric representation of such server versions for reporting by PQserverVers

[COMMITTERS] pgsql: Teach libpq to decode server version correctly from future serve

2016-08-05 Thread Tom Lane
Teach libpq to decode server version correctly from future servers. Beginning with the next development cycle, PG servers will report two-part not three-part version numbers. Fix libpq so that it will compute the correct numeric representation of such server versions for reporting by PQserverVers

[COMMITTERS] pgsql: Teach libpq to decode server version correctly from future serve

2016-08-05 Thread Tom Lane
Teach libpq to decode server version correctly from future servers. Beginning with the next development cycle, PG servers will report two-part not three-part version numbers. Fix libpq so that it will compute the correct numeric representation of such server versions for reporting by PQserverVers

[COMMITTERS] pgsql: Fix copy-and-pasteo in 81c766b3fd41c78c634d78ebae8d316808dfc630.

2016-08-05 Thread Tom Lane
Fix copy-and-pasteo in 81c766b3fd41c78c634d78ebae8d316808dfc630. Report: <[email protected]> Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/fc509cd82443a4cf338032492f6b1bd6e8698f8d Modified Files -- src/include/utils/tqual.h | 2 +- 1 file ch

Re: [COMMITTERS] pgsql: Change InitToastSnapshot to a macro.

2016-08-05 Thread Tom Lane
Andrew Dunstan writes: > Appears to have caused some buildfarm failures on the decoding tests. Argh ... obvious typo, which I failed to see either. Will fix. regards, tom lane -- Sent via pgsql-committers mailing list ([email protected]) To make changes

[COMMITTERS] pgsql: Make array_to_tsvector() sort and de-duplicate the given strings

2016-08-05 Thread Tom Lane
Make array_to_tsvector() sort and de-duplicate the given strings. This is required for the result to be a legal tsvector value. Noted while fooling with Andreas Seltenreich's ts_delete() crash. Discussion: <[email protected]> Branch -- master Details --- http://git.postgresql.o

Re: [COMMITTERS] pgsql: Change InitToastSnapshot to a macro.

2016-08-05 Thread Andrew Dunstan
On 08/05/2016 12:04 PM, Robert Haas wrote: Change InitToastSnapshot to a macro. tqual.h is included in some front-end compiles, and a static inline breaks on buildfarm member castoroides. Since the macro is never referenced, it should dodge that problem, although this doesn't seem like the cl

[COMMITTERS] pgsql: Re-pgindent tsvector_op.c.

2016-08-05 Thread Tom Lane
Re-pgindent tsvector_op.c. Messed up by recent commits --- this is annoying me while trying to fix some bugs here. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/33fe7360afdc0bb1820743ea5bfe3fc7d522f6c4 Modified Files -- src/backend/utils/adt/tsvector_o

[COMMITTERS] pgsql: Fix ts_delete(tsvector, text[]) to cope with duplicate array ent

2016-08-05 Thread Tom Lane
Fix ts_delete(tsvector, text[]) to cope with duplicate array entries. Such cases either failed an Assert, or produced a corrupt tsvector in non-Assert builds, as reported by Andreas Seltenreich. The reason is that tsvector_delete_by_indices() just assumed that its input array had no duplicates.

[COMMITTERS] pgsql: docs: re-add spaces before units removed

2016-08-05 Thread Bruce Momjian
docs: re-add spaces before units removed This reverts the spaces before k/M/G/TB units removed for consistency in commit ca0c37b56f4a80ad758774e34c86cc4335583d29. Discussion: [email protected] Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/5ebad9a5

[COMMITTERS] pgsql: Add note about unused arguments for pg_replication_origin_xact_r

2016-08-05 Thread Fujii Masao
Add note about unused arguments for pg_replication_origin_xact_reset() in docs. In 9.5, two arguments were introduced into pg_replication_origin_xact_reset() by mistake while they are actually not used at all. We cannot fix this issue for 9.5 anymore because it needs a catalog version bump. Instea

[COMMITTERS] pgsql: Update time zone data files to tzdata release 2016f.

2016-08-05 Thread Tom Lane
Update time zone data files to tzdata release 2016f. DST law changes in Kemerovo and Novosibirsk. Historical corrections for Azerbaijan, Belarus, and Morocco. Asia/Novokuznetsk and Asia/Novosibirsk now use numeric time zone abbreviations instead of invented ones. Zones for Antarctic bases and o

[COMMITTERS] pgsql: Update time zone data files to tzdata release 2016f.

2016-08-05 Thread Tom Lane
Update time zone data files to tzdata release 2016f. DST law changes in Kemerovo and Novosibirsk. Historical corrections for Azerbaijan, Belarus, and Morocco. Asia/Novokuznetsk and Asia/Novosibirsk now use numeric time zone abbreviations instead of invented ones. Zones for Antarctic bases and o

[COMMITTERS] pgsql: Update time zone data files to tzdata release 2016f.

2016-08-05 Thread Tom Lane
Update time zone data files to tzdata release 2016f. DST law changes in Kemerovo and Novosibirsk. Historical corrections for Azerbaijan, Belarus, and Morocco. Asia/Novokuznetsk and Asia/Novosibirsk now use numeric time zone abbreviations instead of invented ones. Zones for Antarctic bases and o

[COMMITTERS] pgsql: Update time zone data files to tzdata release 2016f.

2016-08-05 Thread Tom Lane
Update time zone data files to tzdata release 2016f. DST law changes in Kemerovo and Novosibirsk. Historical corrections for Azerbaijan, Belarus, and Morocco. Asia/Novokuznetsk and Asia/Novosibirsk now use numeric time zone abbreviations instead of invented ones. Zones for Antarctic bases and o

[COMMITTERS] pgsql: Update time zone data files to tzdata release 2016f.

2016-08-05 Thread Tom Lane
Update time zone data files to tzdata release 2016f. DST law changes in Kemerovo and Novosibirsk. Historical corrections for Azerbaijan, Belarus, and Morocco. Asia/Novokuznetsk and Asia/Novosibirsk now use numeric time zone abbreviations instead of invented ones. Zones for Antarctic bases and o

[COMMITTERS] pgsql: Update time zone data files to tzdata release 2016f.

2016-08-05 Thread Tom Lane
Update time zone data files to tzdata release 2016f. DST law changes in Kemerovo and Novosibirsk. Historical corrections for Azerbaijan, Belarus, and Morocco. Asia/Novokuznetsk and Asia/Novosibirsk now use numeric time zone abbreviations instead of invented ones. Zones for Antarctic bases and o

[COMMITTERS] pgsql: Change InitToastSnapshot to a macro.

2016-08-05 Thread Robert Haas
Change InitToastSnapshot to a macro. tqual.h is included in some front-end compiles, and a static inline breaks on buildfarm member castoroides. Since the macro is never referenced, it should dodge that problem, although this doesn't seem like the cleanest way of hiding things from front-end comp