[COMMITTERS] pgsql: Improve performance of timezone loading, especially pg_timezone_

Improve performance of timezone loading, especially pg_timezone_names view. tzparse() would attempt to load the "posixrules" timezone database file on each call. That might seem like it would only be an issue when selecting a POSIX-style zone name rather than a zone defined in the timezone

[COMMITTERS] pgsql: Improve performance of timezone loading, especially pg_timezone_

Improve performance of timezone loading, especially pg_timezone_names view. tzparse() would attempt to load the "posixrules" timezone database file on each call. That might seem like it would only be an issue when selecting a POSIX-style zone name rather than a zone defined in the timezone

[COMMITTERS] pgsql: Improve performance of timezone loading, especially pg_timezone_

Improve performance of timezone loading, especially pg_timezone_names view. tzparse() would attempt to load the "posixrules" timezone database file on each call. That might seem like it would only be an issue when selecting a POSIX-style zone name rather than a zone defined in the timezone

[COMMITTERS] pgsql: Improve performance of timezone loading, especially pg_timezone_

Improve performance of timezone loading, especially pg_timezone_names view. tzparse() would attempt to load the "posixrules" timezone database file on each call. That might seem like it would only be an issue when selecting a POSIX-style zone name rather than a zone defined in the timezone

[COMMITTERS] pgsql: Improve performance of timezone loading, especially pg_timezone_

Improve performance of timezone loading, especially pg_timezone_names view. tzparse() would attempt to load the "posixrules" timezone database file on each call. That might seem like it would only be an issue when selecting a POSIX-style zone name rather than a zone defined in the timezone

[COMMITTERS] pgsql: Improve performance of timezone loading, especially pg_timezone_

Improve performance of timezone loading, especially pg_timezone_names view. tzparse() would attempt to load the "posixrules" timezone database file on each call. That might seem like it would only be an issue when selecting a POSIX-style zone name rather than a zone defined in the timezone

[COMMITTERS] pgsql: Remove create_singleton_array(), hard-coding the case in its sol

Remove create_singleton_array(), hard-coding the case in its sole caller. create_singleton_array() was not really as useful as we perhaps thought when we added it. It had never accreted more than one call site, and is only saving a dozen lines of code at that one, which is considerably less bulk

[COMMITTERS] pgsql: Ensure commands in extension scripts see the results of precedin

Ensure commands in extension scripts see the results of preceding DDL. Due to a missing CommandCounterIncrement() call, parsing of a non-utility command in an extension script would not see the effects of the immediately preceding DDL command, unless that command's execution ends with

[COMMITTERS] pgsql: Ensure commands in extension scripts see the results of precedin

Ensure commands in extension scripts see the results of preceding DDL. Due to a missing CommandCounterIncrement() call, parsing of a non-utility command in an extension script would not see the effects of the immediately preceding DDL command, unless that command's execution ends with

[COMMITTERS] pgsql: Ensure commands in extension scripts see the results of precedin

Ensure commands in extension scripts see the results of preceding DDL. Due to a missing CommandCounterIncrement() call, parsing of a non-utility command in an extension script would not see the effects of the immediately preceding DDL command, unless that command's execution ends with

[COMMITTERS] pgsql: Ensure commands in extension scripts see the results of precedin

Ensure commands in extension scripts see the results of preceding DDL. Due to a missing CommandCounterIncrement() call, parsing of a non-utility command in an extension script would not see the effects of the immediately preceding DDL command, unless that command's execution ends with

[COMMITTERS] pgsql: Ensure commands in extension scripts see the results of precedin

Ensure commands in extension scripts see the results of preceding DDL. Due to a missing CommandCounterIncrement() call, parsing of a non-utility command in an extension script would not see the effects of the immediately preceding DDL command, unless that command's execution ends with

[COMMITTERS] pgsql: Ensure commands in extension scripts see the results of precedin

Ensure commands in extension scripts see the results of preceding DDL. Due to a missing CommandCounterIncrement() call, parsing of a non-utility command in an extension script would not see the effects of the immediately preceding DDL command, unless that command's execution ends with

[COMMITTERS] pgsql: extstats: change output functions to emit valid JSON

extstats: change output functions to emit valid JSON Manipulating extended statistics is more convenient as JSON than the current ad-hoc format, so let's change before it's too late. Discussion: https://postgr.es/m/20170420193828.k3fliiock5hdnehn@alvherre.pgsql Branch -- master Details

[COMMITTERS] pgsql: doc: Improve order in ALTER PUBLICATION/SUBSCRIPTION ref pages

doc: Improve order in ALTER PUBLICATION/SUBSCRIPTION ref pages Move the OWNER and RENAME clauses to the end, so the interesting functionality is listed first. This is more typical on nearby reference pages, whereas the previous order was the order in which the clauses were added. Branch --

[COMMITTERS] pgsql: Fix typos in comments.

Fix typos in comments. Etsuro Fujita Discussion: http://postgr.es/m/00e88999-684d-d79a-70e4-908c937a0...@lab.ntt.co.jp Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/0d1e1f0ea45c15170c2d2ae0f0c448bc2d2b72d9 Modified Files --

[COMMITTERS] pgsql: doc: Add missing markup

doc: Add missing markup Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/460c89f46c1fdf11baa8e76e6d04e1ff87d7e008 Modified Files -- doc/src/sgml/datatype.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers mailing

[COMMITTERS] pgsql: Avoid unnecessary catalog updates in ALTER SEQUENCE

Avoid unnecessary catalog updates in ALTER SEQUENCE ALTER SEQUENCE can do nontransactional changes to the sequence (RESTART clause) and transactional updates to the pg_sequence catalog (most other clauses). When just calling RESTART, the code would still needlessly do a catalog update without

[COMMITTERS] pgsql: doc: Update ALTER SEQUENCE claims about changes being nontransac

doc: Update ALTER SEQUENCE claims about changes being nontransactional Clarify that all changes except RESTART are transactional (since 1753b1b027035029c2a2a1649065762fafbf63f3). Reported-by: Michael Paquier Branch -- master Details ---

[COMMITTERS] pgsql: Fix perl thinko in commit fed6df486dca

Fix perl thinko in commit fed6df486dca Report and fix from Vaishnavi Prabakaran Backpatch to 9.4 like original. Branch -- REL9_5_STABLE Details --- https://git.postgresql.org/pg/commitdiff/df53413ba524a01cced9c12131606d84d52a0fc9 Modified Files --

[COMMITTERS] pgsql: Fix perl thinko in commit fed6df486dca

Fix perl thinko in commit fed6df486dca Report and fix from Vaishnavi Prabakaran Backpatch to 9.4 like original. Branch -- REL9_4_STABLE Details --- https://git.postgresql.org/pg/commitdiff/b2ed1c8a467c2f8f91323a13696a900f31a3239d Modified Files --

[COMMITTERS] pgsql: Fix perl thinko in commit fed6df486dca

Fix perl thinko in commit fed6df486dca Report and fix from Vaishnavi Prabakaran Backpatch to 9.4 like original. Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitdiff/f06caa09d9c539a2336434e6b521b6541c3da624 Modified Files --

[COMMITTERS] pgsql: Fix perl thinko in commit fed6df486dca

Fix perl thinko in commit fed6df486dca Report and fix from Vaishnavi Prabakaran Backpatch to 9.4 like original. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/9a0d2008c3fe82c9d62a81e87cd0c4de1be09e0f Modified Files -- src/tools/msvc/vcregress.pl | 2

[COMMITTERS] pgsql: Change hot_standby default value to 'on'

Change hot_standby default value to 'on' This goes together with the changes made to enable replication on the sending side by default (wal_level, max_wal_senders etc) by making the receiving stadby node also enable it by default. Huong Dangminh Branch -- master Details ---