[COMMITTERS] pgsql: docs: re-add instructions on setting wal_level for rsync use
docs: re-add instructions on setting wal_level for rsync use This step was erroneously removed four days ago by me. Reported-by: Magnus via IM Backpatch-through: 9.5 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/00210e3fb974ff2b9affc4d8f3b29f9cb3645a60 Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: docs: re-add instructions on setting wal_level for rsync use
docs: re-add instructions on setting wal_level for rsync use This step was erroneously removed four days ago by me. Reported-by: Magnus via IM Backpatch-through: 9.5 Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitdiff/95a231aef9bb872913f67f30a8cffcfefaf8ca51 Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: docs: re-add instructions on setting wal_level for rsync use
docs: re-add instructions on setting wal_level for rsync use This step was erroneously removed four days ago by me. Reported-by: Magnus via IM Backpatch-through: 9.5 Branch -- REL9_5_STABLE Details --- https://git.postgresql.org/pg/commitdiff/8aa520045e1427f6f2ee0881e6d551546787da55 Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: docs: re-add instructions on setting wal_level for rsync use
docs: re-add instructions on setting wal_level for rsync use This step was erroneously removed four days ago by me. Reported-by: Magnus via IM Backpatch-through: 9.5 Branch -- REL_10_STABLE Details --- https://git.postgresql.org/pg/commitdiff/4131cc6b90ce274a44462627a1c878bf1950838b Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: add example of % substitution for connection URIs
doc: add example of % substitution for connection URIs Reported-by: Zhou Digoal Discussion: https://postgr.es/m/20170912133722.25637...@wrigleys.postgresql.org Backpatch-through: 10 Branch -- REL_10_STABLE Details --- https://git.postgresql.org/pg/commitdiff/ba01ef267ee48e86566886376c41d0a20551713c Modified Files -- doc/src/sgml/libpq.sgml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: add example of % substitution for connection URIs
doc: add example of % substitution for connection URIs Reported-by: Zhou Digoal Discussion: https://postgr.es/m/20170912133722.25637...@wrigleys.postgresql.org Backpatch-through: 10 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/d61f5bb7c444255b064a60df782907f7dddad61a Modified Files -- doc/src/sgml/libpq.sgml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: docs: clarify pg_upgrade docs regarding standbys and rsync
docs: clarify pg_upgrade docs regarding standbys and rsync Document that rsync is an _optional_ way to upgrade standbys, suggest rsync option --dry-run, and mention a way of upgrading one standby from another using rsync. Also clarify some instructions by specifying if they operate on the old or new clusters. Reported-by: Stephen Frost, Magnus Hagander Discussion: https://postgr.es/m/20170914191250.gb6...@momjian.us Backpatch-through: 9.5 Branch -- REL_10_STABLE Details --- https://git.postgresql.org/pg/commitdiff/d2bbd6104096b1559c1683d39e2c4e4cfbcada1c Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 41 - 1 file changed, 24 insertions(+), 17 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: docs: clarify pg_upgrade docs regarding standbys and rsync
docs: clarify pg_upgrade docs regarding standbys and rsync Document that rsync is an _optional_ way to upgrade standbys, suggest rsync option --dry-run, and mention a way of upgrading one standby from another using rsync. Also clarify some instructions by specifying if they operate on the old or new clusters. Reported-by: Stephen Frost, Magnus Hagander Discussion: https://postgr.es/m/20170914191250.gb6...@momjian.us Backpatch-through: 9.5 Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitdiff/c4c45945e27c9fc90b0dcb1d9af7fd6ea5220f81 Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 41 - 1 file changed, 24 insertions(+), 17 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: docs: clarify pg_upgrade docs regarding standbys and rsync
docs: clarify pg_upgrade docs regarding standbys and rsync Document that rsync is an _optional_ way to upgrade standbys, suggest rsync option --dry-run, and mention a way of upgrading one standby from another using rsync. Also clarify some instructions by specifying if they operate on the old or new clusters. Reported-by: Stephen Frost, Magnus Hagander Discussion: https://postgr.es/m/20170914191250.gb6...@momjian.us Backpatch-through: 9.5 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/04b64b8ddf9926950fe86d7d489825c46665dc01 Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 41 - 1 file changed, 24 insertions(+), 17 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: docs: clarify pg_upgrade docs regarding standbys and rsync
docs: clarify pg_upgrade docs regarding standbys and rsync Document that rsync is an _optional_ way to upgrade standbys, suggest rsync option --dry-run, and mention a way of upgrading one standby from another using rsync. Also clarify some instructions by specifying if they operate on the old or new clusters. Reported-by: Stephen Frost, Magnus Hagander Discussion: https://postgr.es/m/20170914191250.gb6...@momjian.us Backpatch-through: 9.5 Branch -- REL9_5_STABLE Details --- https://git.postgresql.org/pg/commitdiff/2efe122c5a479c03493995adadc8c80bec8015da Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 41 - 1 file changed, 24 insertions(+), 17 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: docs: adjust "link mode" mention in pg_upgrade streaming steps
docs: adjust "link mode" mention in pg_upgrade streaming steps Backpatch-through: 9.5 Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitdiff/e5c8d43abde8cbb4b7fbbb5a215e497f11bf6fe6 Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: docs: adjust "link mode" mention in pg_upgrade streaming steps
docs: adjust "link mode" mention in pg_upgrade streaming steps Backpatch-through: 9.5 Branch -- REL_10_STABLE Details --- https://git.postgresql.org/pg/commitdiff/6dffdcfeef934eb21b8a767d8be11ec33ccb56ed Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: docs: adjust "link mode" mention in pg_upgrade streaming steps
docs: adjust "link mode" mention in pg_upgrade streaming steps Backpatch-through: 9.5 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/82e367ddbfdf798ea8a30da15db3984017277342 Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: docs: adjust "link mode" mention in pg_upgrade streaming steps
docs: adjust "link mode" mention in pg_upgrade streaming steps Backpatch-through: 9.5 Branch -- REL9_5_STABLE Details --- https://git.postgresql.org/pg/commitdiff/e1795efcbecdcb53d3910cd46a067a1e66ab0938 Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: docs: improve pg_upgrade standby instructions
docs: improve pg_upgrade standby instructions This makes it clear that pg_upgrade standby upgrade instructions should only be used in link mode, adds examples, and explains how rsync works with links. Reported-by: Andreas Joseph Krogh Discussion: https://postgr.es/m/VisenaEmail.6c.c0e592c5af4ef0a2.15e785dcb61@tc7-visena Backpatch-through: 9.5 Branch -- REL9_5_STABLE Details --- https://git.postgresql.org/pg/commitdiff/213409c6a3ed9d8976985b76f51822c32a710691 Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 64 ++--- 1 file changed, 41 insertions(+), 23 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: docs: improve pg_upgrade standby instructions
docs: improve pg_upgrade standby instructions This makes it clear that pg_upgrade standby upgrade instructions should only be used in link mode, adds examples, and explains how rsync works with links. Reported-by: Andreas Joseph Krogh Discussion: https://postgr.es/m/VisenaEmail.6c.c0e592c5af4ef0a2.15e785dcb61@tc7-visena Backpatch-through: 9.5 Branch -- REL_10_STABLE Details --- https://git.postgresql.org/pg/commitdiff/aaa4faa7a00cb85322e570f2d148a51b95b847c4 Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 64 ++--- 1 file changed, 41 insertions(+), 23 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: docs: improve pg_upgrade standby instructions
docs: improve pg_upgrade standby instructions This makes it clear that pg_upgrade standby upgrade instructions should only be used in link mode, adds examples, and explains how rsync works with links. Reported-by: Andreas Joseph Krogh Discussion: https://postgr.es/m/VisenaEmail.6c.c0e592c5af4ef0a2.15e785dcb61@tc7-visena Backpatch-through: 9.5 Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitdiff/3b3327ef2762bf6753ccd5bee75a4935a09bd0a1 Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 64 ++--- 1 file changed, 41 insertions(+), 23 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: docs: improve pg_upgrade standby instructions
docs: improve pg_upgrade standby instructions This makes it clear that pg_upgrade standby upgrade instructions should only be used in link mode, adds examples, and explains how rsync works with links. Reported-by: Andreas Joseph Krogh Discussion: https://postgr.es/m/VisenaEmail.6c.c0e592c5af4ef0a2.15e785dcb61@tc7-visena Backpatch-through: 9.5 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/9521ce4a7a1125385fb4de9689f345db594c516a Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 64 ++--- 1 file changed, 41 insertions(+), 23 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: docs: improve pg_upgrade rsync instructions
docs: improve pg_upgrade rsync instructions This explains how rsync accomplishes updating standby servers and clarifies the instructions. Reported-by: Andreas Joseph Krogh Discussion: https://postgr.es/m/VisenaEmail.10.2b4049e43870bd16.15d898d696f@tc7-visena Backpatch-through: 9.5 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/2d4a614e1ec34a746aca43d6a02aa3344dcf5fd4 Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 40 1 file changed, 24 insertions(+), 16 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: docs: improve pg_upgrade rsync instructions
docs: improve pg_upgrade rsync instructions This explains how rsync accomplishes updating standby servers and clarifies the instructions. Reported-by: Andreas Joseph Krogh Discussion: https://postgr.es/m/VisenaEmail.10.2b4049e43870bd16.15d898d696f@tc7-visena Backpatch-through: 9.5 Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitdiff/8d787bd66c8f64db85e0102f1dc1a0978d060fa1 Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 42 - 1 file changed, 25 insertions(+), 17 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: docs: improve pg_upgrade rsync instructions
docs: improve pg_upgrade rsync instructions This explains how rsync accomplishes updating standby servers and clarifies the instructions. Reported-by: Andreas Joseph Krogh Discussion: https://postgr.es/m/VisenaEmail.10.2b4049e43870bd16.15d898d696f@tc7-visena Backpatch-through: 9.5 Branch -- REL_10_STABLE Details --- https://git.postgresql.org/pg/commitdiff/b1705f35f805933629520eded68b82d2a2900871 Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 40 1 file changed, 24 insertions(+), 16 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: docs: improve pg_upgrade rsync instructions
docs: improve pg_upgrade rsync instructions This explains how rsync accomplishes updating standby servers and clarifies the instructions. Reported-by: Andreas Joseph Krogh Discussion: https://postgr.es/m/VisenaEmail.10.2b4049e43870bd16.15d898d696f@tc7-visena Backpatch-through: 9.5 Branch -- REL9_5_STABLE Details --- https://git.postgresql.org/pg/commitdiff/5d2e18d6ec3bdc042a37b1a9e577679e4b829bea Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 38 -- 1 file changed, 24 insertions(+), 14 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: PG 10 release notes: change trigger transition tables
PG 10 release notes: change trigger transition tables Add attribution of trigger transition tables for Thomas Munro. Reported-by: Thomas Munro Discussion: https://postgr.es/m/CAEepm=2bDFgr4ut+1-QjKQY4MA=5ek8ap3nyb19y2tptl6x...@mail.gmail.com Backpatch-through: 10 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/57e1c007939447ecf8c2d2aa2f507124613324ad Modified Files -- doc/src/sgml/release-10.sgml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: PG 10 release notes: change trigger transition tables
PG 10 release notes: change trigger transition tables Add attribution of trigger transition tables for Thomas Munro. Reported-by: Thomas Munro Discussion: https://postgr.es/m/CAEepm=2bDFgr4ut+1-QjKQY4MA=5ek8ap3nyb19y2tptl6x...@mail.gmail.com Backpatch-through: 10 Branch -- REL_10_STABLE Details --- https://git.postgresql.org/pg/commitdiff/d4c9eb005a16ff5cdc9d5d9514a3195c60ad21ab Modified Files -- doc/src/sgml/release-10.sgml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: PG 10 release notes: update PL/Tcl functions item
PG 10 release notes: update PL/Tcl functions item Update attribution of PL/Tcl functions item from Jim Nasby to Karl Lehenbauer. Reported-by: Jim Nasby Discussion: https://postgr.es/m/ed42f3d6-4251-dabc-747f-1ff936763...@nasby.net Backpatch-through: 10 Branch -- REL_10_STABLE Details --- https://git.postgresql.org/pg/commitdiff/1d27a7004d84516f5d04662c1cd52f41400b7750 Modified Files -- doc/src/sgml/release-10.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: PG 10 release notes: update PL/Tcl functions item
PG 10 release notes: update PL/Tcl functions item Update attribution of PL/Tcl functions item from Jim Nasby to Karl Lehenbauer. Reported-by: Jim Nasby Discussion: https://postgr.es/m/ed42f3d6-4251-dabc-747f-1ff936763...@nasby.net Backpatch-through: 10 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/3126433ae7464ffc25a8317110e79defaa3d8865 Modified Files -- doc/src/sgml/release-10.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Adjust pgindent script to use pg_bsd_indent 2.0.
On Wed, Jun 21, 2017 at 06:26:29PM +, Tom Lane wrote: > Adjust pgindent script to use pg_bsd_indent 2.0. > > Update version-checking code and list of switches. Delete obsolete > quasi-support for using GNU indent. Remove a lot of no-longer-needed > workarounds for bugs of the old version, and improve comments for > the hacks that remain. Update run_build() subroutine to fetch the Another hack of mine bits the dust. I see a few did remain. :-) -- Bruce Momjian <br...@momjian.us>http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: pg_upgrade: start/stop new server after pg_resetwal
pg_upgrade: start/stop new server after pg_resetwal When commit 0f33a719fdbb5d8c43839ea0d2c90cd03e2af2d2 removed the instructions to start/stop the new cluster before running rsync, it was now possible for pg_resetwal/pg_resetxlog to leave the final WAL record at wal_level=minimum, preventing upgraded standby servers from reconnecting. This patch fixes that by having pg_upgrade unconditionally start/stop the new cluster after pg_resetwal/pg_resetxlog has run. Backpatch through 9.2 since, though the instructions were added in PG 9.5, they worked all the way back to 9.2. Discussion: https://postgr.es/m/20170620171844.gc24...@momjian.us Backpatch-through: 9.2 Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitdiff/0efdbd323e53091779ddc3f048123214612a76f9 Modified Files -- src/bin/pg_upgrade/check.c | 16 +++- src/bin/pg_upgrade/pg_upgrade.c | 2 +- src/bin/pg_upgrade/pg_upgrade.h | 2 +- 3 files changed, 13 insertions(+), 7 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: pg_upgrade: start/stop new server after pg_resetwal
pg_upgrade: start/stop new server after pg_resetwal When commit 0f33a719fdbb5d8c43839ea0d2c90cd03e2af2d2 removed the instructions to start/stop the new cluster before running rsync, it was now possible for pg_resetwal/pg_resetxlog to leave the final WAL record at wal_level=minimum, preventing upgraded standby servers from reconnecting. This patch fixes that by having pg_upgrade unconditionally start/stop the new cluster after pg_resetwal/pg_resetxlog has run. Backpatch through 9.2 since, though the instructions were added in PG 9.5, they worked all the way back to 9.2. Discussion: https://postgr.es/m/20170620171844.gc24...@momjian.us Backpatch-through: 9.2 Branch -- REL9_2_STABLE Details --- https://git.postgresql.org/pg/commitdiff/65beccae51fc0bc51cd53651f36b7486902869fb Modified Files -- contrib/pg_upgrade/check.c | 19 +++ contrib/pg_upgrade/pg_upgrade.c | 2 +- contrib/pg_upgrade/pg_upgrade.h | 2 +- 3 files changed, 13 insertions(+), 10 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: pg_upgrade: start/stop new server after pg_resetwal
pg_upgrade: start/stop new server after pg_resetwal When commit 0f33a719fdbb5d8c43839ea0d2c90cd03e2af2d2 removed the instructions to start/stop the new cluster before running rsync, it was now possible for pg_resetwal/pg_resetxlog to leave the final WAL record at wal_level=minimum, preventing upgraded standby servers from reconnecting. This patch fixes that by having pg_upgrade unconditionally start/stop the new cluster after pg_resetwal/pg_resetxlog has run. Backpatch through 9.2 since, though the instructions were added in PG 9.5, they worked all the way back to 9.2. Discussion: https://postgr.es/m/20170620171844.gc24...@momjian.us Backpatch-through: 9.2 Branch -- REL9_3_STABLE Details --- https://git.postgresql.org/pg/commitdiff/5c890645d9c4f57d49110e7943914c11012d3e85 Modified Files -- contrib/pg_upgrade/check.c | 19 +++ contrib/pg_upgrade/pg_upgrade.c | 2 +- contrib/pg_upgrade/pg_upgrade.h | 2 +- 3 files changed, 13 insertions(+), 10 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: pg_upgrade: start/stop new server after pg_resetwal
pg_upgrade: start/stop new server after pg_resetwal When commit 0f33a719fdbb5d8c43839ea0d2c90cd03e2af2d2 removed the instructions to start/stop the new cluster before running rsync, it was now possible for pg_resetwal/pg_resetxlog to leave the final WAL record at wal_level=minimum, preventing upgraded standby servers from reconnecting. This patch fixes that by having pg_upgrade unconditionally start/stop the new cluster after pg_resetwal/pg_resetxlog has run. Backpatch through 9.2 since, though the instructions were added in PG 9.5, they worked all the way back to 9.2. Discussion: https://postgr.es/m/20170620171844.gc24...@momjian.us Backpatch-through: 9.2 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/b710248dd3f90c46bd4208e6bf1290048b9d76cd Modified Files -- src/bin/pg_upgrade/check.c | 20 +++- src/bin/pg_upgrade/pg_upgrade.c | 2 +- src/bin/pg_upgrade/pg_upgrade.h | 2 +- 3 files changed, 13 insertions(+), 11 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: pg_upgrade: start/stop new server after pg_resetwal
pg_upgrade: start/stop new server after pg_resetwal When commit 0f33a719fdbb5d8c43839ea0d2c90cd03e2af2d2 removed the instructions to start/stop the new cluster before running rsync, it was now possible for pg_resetwal/pg_resetxlog to leave the final WAL record at wal_level=minimum, preventing upgraded standby servers from reconnecting. This patch fixes that by having pg_upgrade unconditionally start/stop the new cluster after pg_resetwal/pg_resetxlog has run. Backpatch through 9.2 since, though the instructions were added in PG 9.5, they worked all the way back to 9.2. Discussion: https://postgr.es/m/20170620171844.gc24...@momjian.us Backpatch-through: 9.2 Branch -- REL9_5_STABLE Details --- https://git.postgresql.org/pg/commitdiff/f4f867bda33604cf82a8c74a874dfb20a0270595 Modified Files -- src/bin/pg_upgrade/check.c | 16 +++- src/bin/pg_upgrade/pg_upgrade.c | 2 +- src/bin/pg_upgrade/pg_upgrade.h | 2 +- 3 files changed, 13 insertions(+), 7 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: pg_upgrade: start/stop new server after pg_resetwal
pg_upgrade: start/stop new server after pg_resetwal When commit 0f33a719fdbb5d8c43839ea0d2c90cd03e2af2d2 removed the instructions to start/stop the new cluster before running rsync, it was now possible for pg_resetwal/pg_resetxlog to leave the final WAL record at wal_level=minimum, preventing upgraded standby servers from reconnecting. This patch fixes that by having pg_upgrade unconditionally start/stop the new cluster after pg_resetwal/pg_resetxlog has run. Backpatch through 9.2 since, though the instructions were added in PG 9.5, they worked all the way back to 9.2. Discussion: https://postgr.es/m/20170620171844.gc24...@momjian.us Backpatch-through: 9.2 Branch -- REL9_4_STABLE Details --- https://git.postgresql.org/pg/commitdiff/a0e8548811f6a4a47fe747fea72edcc3c4bf3f27 Modified Files -- contrib/pg_upgrade/check.c | 19 +++ contrib/pg_upgrade/pg_upgrade.c | 2 +- contrib/pg_upgrade/pg_upgrade.h | 2 +- 3 files changed, 13 insertions(+), 10 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: adjust wal_level pg_upgrade patch
doc: adjust wal_level pg_upgrade patch Since 9.5 has two WAL levels that apply to standby upgrades, archive and hot_standby, adjust the docs for that version to say, basically, "restore old cluster wal_level value in the new cluster". This is a follow-on patch to fd376afc9863dd8ea3eba95edfa79961173e706f. Backpatch-through: 9.5 only Branch -- REL9_5_STABLE Details --- https://git.postgresql.org/pg/commitdiff/525ee8ff333d71fcf155833ea59a635f30b87fd1 Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: remove mention of Windows junction points by pg_upgrade
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: https://postgr.es/m/6a638c60-90bb-4921-8ee4-5fdad68f8...@aklaver.com Backpatch-through: 9.3, where the mention first appeared Branch -- REL9_3_STABLE Details --- https://git.postgresql.org/pg/commitdiff/ae58c15bd3f6447cbc67256bfb0b40d342b88fec Modified Files -- doc/src/sgml/pgupgrade.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: remove mention of Windows junction points by pg_upgrade
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: https://postgr.es/m/6a638c60-90bb-4921-8ee4-5fdad68f8...@aklaver.com Backpatch-through: 9.3, where the mention first appeared Branch -- REL9_4_STABLE Details --- https://git.postgresql.org/pg/commitdiff/ad1ea61cf88a02f5983dff2d2342136a97675c29 Modified Files -- doc/src/sgml/pgupgrade.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: remove mention of Windows junction points by pg_upgrade
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: https://postgr.es/m/6a638c60-90bb-4921-8ee4-5fdad68f8...@aklaver.com Backpatch-through: 9.3, where the mention first appeared Branch -- REL9_5_STABLE Details --- https://git.postgresql.org/pg/commitdiff/85f2f543a81aebd1bc214679693c8720ad462fcd Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: remove mention of Windows junction points by pg_upgrade
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: https://postgr.es/m/6a638c60-90bb-4921-8ee4-5fdad68f8...@aklaver.com Backpatch-through: 9.3, where the mention first appeared Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitdiff/1798dd153d6f513c56c2888bcd72f3de854f4d78 Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: remove mention of Windows junction points by pg_upgrade
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: https://postgr.es/m/6a638c60-90bb-4921-8ee4-5fdad68f8...@aklaver.com Backpatch-through: 9.3, where the mention first appeared Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/07fb943335f3cdd11a9146ae6fdee237cc83c5f6 Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: docs: Fix pg_upgrade standby server upgrade docs
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 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/0f33a719fdbb5d8c43839ea0d2c90cd03e2af2d2 Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 33 +++-- 1 file changed, 15 insertions(+), 18 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: docs: Fix pg_upgrade standby server upgrade docs
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 Branch -- REL9_5_STABLE Details --- https://git.postgresql.org/pg/commitdiff/fd376afc9863dd8ea3eba95edfa79961173e706f Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 33 +++-- 1 file changed, 15 insertions(+), 18 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: docs: Fix pg_upgrade standby server upgrade docs
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 Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitdiff/a0873fbabb9e9eebb65cf1891c6f1b11290fcd4e Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 33 +++-- 1 file changed, 15 insertions(+), 18 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Assert that we don't invent relfilenodes or type OIDs in binary
On Tue, Jun 13, 2017 at 03:10:16PM -0400, Tom Lane wrote: > Bruce Momjian <br...@momjian.us> writes: > > On Tue, Jun 13, 2017 at 11:52:04AM -0700, Andres Freund wrote: > >> I'm not sure what you're actually concerned about here? > > > I am concerned a non-assert build will not error out, but if no one else > > is concerned about that, I am fine. > > I think in a production situation, we actually don't want it to error > out. The odds are fairly good that the run would complete successfully > (ie, the potential OID collision never actually materializes). So all > we're doing is converting a possible failure into an unavoidable one. > > Where we want to hear about the problem is in development. So really > an Assert is the right thing. OK, but my point is that all the other places, which seems similar, error out in production. -- Bruce Momjian <br...@momjian.us>http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Assert that we don't invent relfilenodes or type OIDs in binary
On Tue, Jun 13, 2017 at 11:52:04AM -0700, Andres Freund wrote: > On 2017-06-13 13:45:12 -0400, Bruce Momjian wrote: > > On Tue, Jun 13, 2017 at 01:39:34PM -0400, Tom Lane wrote: > > > Bruce Momjian <br...@momjian.us> writes: > > > > Uh, is there a reason this is only an Assert(), meaning it only checks > > > > in assert builds. pg_upgrade already has a lot of checks and they are > > > > all fatal. > > > > > > Yeah, I didn't think it was worth adding overhead to production builds > > > for it. > > > > Uh, you realize there are already many pg_upgrade sanity checks in the > > backend that are not asserts, right? > > And? Not that it'll make a huge difference, but GetNewOidWithIndex() is > a relatively hot-path in some workloads (e.g. with lots of toasted > data), so it actually can make a difference. And for debugging asserts > are often actually more useful, because you get a backtrace. > > I'm not sure what you're actually concerned about here? I am concerned a non-assert build will not error out, but if no one else is concerned about that, I am fine. -- Bruce Momjian <br...@momjian.us>http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Assert that we don't invent relfilenodes or type OIDs in binary
On Tue, Jun 13, 2017 at 01:39:34PM -0400, Tom Lane wrote: > Bruce Momjian <br...@momjian.us> writes: > > Uh, is there a reason this is only an Assert(), meaning it only checks > > in assert builds. pg_upgrade already has a lot of checks and they are > > all fatal. > > Yeah, I didn't think it was worth adding overhead to production builds > for it. Uh, you realize there are already many pg_upgrade sanity checks in the backend that are not asserts, right? -- Bruce Momjian <br...@momjian.us>http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Assert that we don't invent relfilenodes or type OIDs in binary
Uh, is there a reason this is only an Assert(), meaning it only checks in assert builds. pg_upgrade already has a lot of checks and they are all fatal. --- On Tue, Jun 13, 2017 at 12:04:48AM +, Tom Lane wrote: > 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: https://postgr.es/m/19785.1497215...@sss.pgh.pa.us > > Branch > -- > REL9_6_STABLE > > Details > --- > https://git.postgresql.org/pg/commitdiff/318fd99ce7e775158c87b8515780f2663d2df429 > > Modified Files > -- > src/backend/catalog/catalog.c | 16 > 1 file changed, 16 insertions(+) > > > -- > Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-committers -- Bruce Momjian <br...@momjian.us>http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: remove duplicate PG 10 release notes entry
doc: remove duplicate PG 10 release notes entry Reported-by: Daniel Gustafsson Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/f6d5d22ea9497aecdfdfa92717a11f0bcdf17223 Modified Files -- doc/src/sgml/release-10.sgml | 11 --- 1 file changed, 11 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: fix PG 10 release notes with proper attribution and commit
doc: fix PG 10 release notes with proper attribution and commit Fix for hot_standby=on change. Reported-by: Huong Dangminh Author: Huong Dangminh Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/f45d86d762b8bcdac42d5448734016242a1d738b Modified Files -- doc/src/sgml/release-10.sgml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Post-PG 10 beta1 pgperltidy run
Post-PG 10 beta1 pgperltidy run Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/ce554810329b9b8e862eade08b598148931eb456 Modified Files -- contrib/intarray/bench/bench.pl| 3 +- src/backend/catalog/Catalog.pm | 16 +- src/backend/catalog/genbki.pl | 25 +- src/backend/parser/check_keywords.pl | 3 +- src/backend/utils/Gen_fmgrtab.pl | 20 +- src/backend/utils/mb/Unicode/UCS_to_BIG5.pl| 29 +- src/backend/utils/mb/Unicode/UCS_to_EUC_CN.pl | 17 +- .../utils/mb/Unicode/UCS_to_EUC_JIS_2004.pl| 32 +- src/backend/utils/mb/Unicode/UCS_to_EUC_JP.pl | 478 ++ src/backend/utils/mb/Unicode/UCS_to_EUC_KR.pl | 24 +- src/backend/utils/mb/Unicode/UCS_to_EUC_TW.pl | 17 +- src/backend/utils/mb/Unicode/UCS_to_GB18030.pl | 11 +- src/backend/utils/mb/Unicode/UCS_to_JOHAB.pl | 24 +- .../utils/mb/Unicode/UCS_to_SHIFT_JIS_2004.pl | 30 +- src/backend/utils/mb/Unicode/UCS_to_SJIS.pl| 72 ++- src/backend/utils/mb/Unicode/UCS_to_UHC.pl | 19 +- src/backend/utils/mb/Unicode/convutils.pm | 240 + src/bin/initdb/t/001_initdb.pl | 1 + src/bin/pg_basebackup/t/010_pg_basebackup.pl | 40 +- src/bin/pg_basebackup/t/030_pg_recvlogical.pl | 30 +- src/bin/pg_ctl/t/001_start_stop.pl | 11 +- src/bin/pg_ctl/t/003_promote.pl| 42 +- src/bin/pg_dump/t/002_pg_dump.pl | 558 +++-- src/bin/pg_dump/t/010_dump_connstr.pl | 4 +- src/bin/scripts/t/010_clusterdb.pl | 2 +- src/bin/scripts/t/090_reindexdb.pl | 12 +- src/bin/scripts/t/100_vacuumdb.pl | 2 +- src/bin/scripts/t/200_connstr.pl | 23 +- src/common/unicode/generate-unicode_norm_table.pl | 7 +- src/interfaces/libpq/test/regress.pl | 3 +- src/pl/plperl/plc_perlboot.pl | 3 +- src/pl/plperl/plc_trusted.pl | 3 +- src/test/authentication/t/001_password.pl | 32 +- src/test/authentication/t/002_saslprep.pl | 35 +- src/test/modules/commit_ts/t/002_standby.pl| 3 +- src/test/modules/commit_ts/t/004_restart.pl| 4 +- src/test/modules/test_pg_dump/t/001_base.pl| 70 +-- src/test/perl/PostgresNode.pm | 116 +++-- src/test/perl/TestLib.pm | 5 +- src/test/recovery/t/001_stream_rep.pl | 122 +++-- src/test/recovery/t/003_recovery_targets.pl| 10 +- src/test/recovery/t/004_timeline_switch.pl | 6 +- src/test/recovery/t/005_replay_delay.pl| 3 +- src/test/recovery/t/006_logical_decoding.pl| 109 ++-- src/test/recovery/t/007_sync_rep.pl| 18 +- src/test/recovery/t/008_fsm_truncation.pl | 32 +- src/test/recovery/t/009_twophase.pl| 100 ++-- .../recovery/t/010_logical_decoding_timelines.pl | 59 ++- src/test/recovery/t/011_crash_recovery.pl | 26 +- src/test/recovery/t/012_subtransactions.pl | 131 +++-- src/test/ssl/ServerSetup.pm| 17 +- src/test/subscription/t/001_rep_changes.pl | 132 ++--- src/test/subscription/t/002_types.pl | 35 +- src/test/subscription/t/003_constraints.pl | 31 +- src/test/subscription/t/004_sync.pl| 54 +- src/test/subscription/t/005_encoding.pl| 32 +- src/tools/fix-old-flex-code.pl | 3 +- src/tools/msvc/Install.pm | 16 +- src/tools/msvc/Mkvcbuild.pm| 26 +- src/tools/msvc/Solution.pm | 10 +- src/tools/msvc/build.pl| 9 +- src/tools/msvc/config_default.pl | 2 +- src/tools/msvc/gendef.pl | 2 +- src/tools/msvc/pgflex.pl | 3 + src/tools/msvc/vcregress.pl| 3 +- src/tools/pgindent/pgindent| 2 +- 66 files changed, 1872 insertions(+), 1187 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Post-PG 10 beta1 pgindent run
Post-PG 10 beta1 pgindent run perltidy run not included. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/a6fd7b7a5f7bf3a8aa3f3d076cf09d922c1c6dd2 Modified Files -- contrib/bloom/blinsert.c | 10 +- contrib/bloom/blutils.c| 2 +- contrib/btree_gin/btree_gin.c | 32 +- contrib/btree_gist/btree_cash.c| 2 +- contrib/btree_gist/btree_date.c| 2 +- contrib/btree_gist/btree_enum.c| 10 +- contrib/btree_gist/btree_float4.c | 2 +- contrib/btree_gist/btree_float8.c | 2 +- contrib/btree_gist/btree_inet.c| 2 +- contrib/btree_gist/btree_int2.c| 2 +- contrib/btree_gist/btree_int4.c| 2 +- contrib/btree_gist/btree_int8.c| 2 +- contrib/btree_gist/btree_interval.c| 2 +- contrib/btree_gist/btree_oid.c | 2 +- contrib/btree_gist/btree_time.c| 2 +- contrib/btree_gist/btree_ts.c | 4 +- contrib/btree_gist/btree_utils_num.h | 14 +- contrib/btree_gist/btree_utils_var.c | 6 +- contrib/btree_gist/btree_utils_var.h | 12 +- contrib/btree_gist/btree_uuid.c| 2 +- contrib/dblink/dblink.c| 31 +- contrib/oid2name/oid2name.c| 2 +- contrib/pageinspect/brinfuncs.c| 4 +- contrib/pageinspect/hashfuncs.c| 20 +- contrib/pageinspect/rawpage.c | 4 +- contrib/pg_standby/pg_standby.c| 2 +- contrib/pg_visibility/pg_visibility.c | 4 +- contrib/pgcrypto/openssl.c | 8 +- contrib/pgcrypto/pgcrypto.c| 4 +- contrib/pgrowlocks/pgrowlocks.c| 5 +- contrib/pgstattuple/pgstatapprox.c | 2 +- contrib/pgstattuple/pgstatindex.c | 38 +- contrib/postgres_fdw/deparse.c | 16 +- contrib/postgres_fdw/postgres_fdw.c| 22 +- contrib/postgres_fdw/postgres_fdw.h| 4 +- src/backend/access/brin/brin.c | 17 +- src/backend/access/brin/brin_revmap.c | 8 +- src/backend/access/brin/brin_xlog.c| 4 +- src/backend/access/common/printsimple.c| 8 +- src/backend/access/gin/ginvacuum.c | 42 +- src/backend/access/hash/hash.c | 28 +- src/backend/access/hash/hash_xlog.c| 40 +- src/backend/access/hash/hashinsert.c | 51 ++- src/backend/access/hash/hashpage.c | 50 ++- src/backend/access/hash/hashutil.c | 27 +- src/backend/access/heap/heapam.c | 31 +- src/backend/access/nbtree/nbtree.c | 12 +- src/backend/access/rmgrdesc/brindesc.c | 2 +- src/backend/access/rmgrdesc/clogdesc.c | 2 +- src/backend/access/rmgrdesc/gindesc.c | 12 +- src/backend/access/spgist/spginsert.c | 8 +- src/backend/access/transam/clog.c | 12 +- src/backend/access/transam/commit_ts.c | 8 +- src/backend/access/transam/subtrans.c | 14 +- src/backend/access/transam/twophase.c | 109 +++--- src/backend/access/transam/varsup.c| 2 +- src/backend/access/transam/xact.c | 9 +- src/backend/access/transam/xlog.c | 112 +++--- src/backend/access/transam/xlogfuncs.c | 5 +- src/backend/access/transam/xloginsert.c| 23 +- src/backend/access/transam/xlogreader.c| 4 +- src/backend/access/transam/xlogutils.c | 57 +-- src/backend/catalog/dependency.c | 8 +- src/backend/catalog/heap.c | 8 +- src/backend/catalog/objectaddress.c| 34 +- src/backend/catalog/pg_collation.c | 28 +- src/backend/catalog/pg_depend.c| 6 +- src/backend/catalog/pg_inherits.c | 12 +- src/backend/catalog/pg_namespace.c | 2 +- src/backend/catalog/pg_publication.c | 66 ++-- src/backend/catalog/pg_subscription.c | 57 +-- src/backend/commands/alter.c | 2 +- src/backend/commands/analyze.c | 2 +- src/backend/commands/collationcmds.c | 38 +- src/backend/commands/copy.c| 4 +- src/backend/commands/dbcommands.c | 7 +- src/backend/commands/define.c | 2 +- src/backend/commands/dropcmds.c| 13 +- src/backend/commands/event_trigger.c | 4 +- src/backend/commands/foreigncmds.c
[COMMITTERS] pgsql: Update typedefs list in prep. for post-PG10 beta1 pgindent run
Update typedefs list in prep. for post-PG10 beta1 pgindent run Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/8a943324780259757c77c56cfc597347d1150cdb Modified Files -- src/tools/pgindent/typedefs.list | 284 +-- 1 file changed, 216 insertions(+), 68 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Add download URL for perltidy version v20090616
Add download URL for perltidy version v20090616 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/df238b43d76fb8e08469f418f570690651baaa7a Modified Files -- src/tools/pgindent/README | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: update the "current as of" date in the PG 10 release notes
doc: update the "current as of" date in the PG 10 release notes Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/de7cca982ca253236051c2a7f6477bee5ce4b045 Modified Files -- doc/src/sgml/release-10.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: update PG 10 release notes for recent changes
doc: update PG 10 release notes for recent changes Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/b91e5b4684d840c903a78e86700b9d906033c2ad Modified Files -- doc/src/sgml/release-10.sgml | 72 ++-- 1 file changed, 70 insertions(+), 2 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: update markup for release note "release date" block
doc: update markup for release note "release date" block This has to be backpatched to all supported releases so release markup added to HEAD and copied to back branches matches the existing markup. Reported-by: Peter Eisentraut Discussion: 2b8a2552-fffa-f7c8-97c5-14db47a87...@2ndquadrant.com Author: initial patch and sample markup by Peter Eisentraut Backpatch-through: 9.2 Branch -- REL9_2_STABLE Details --- https://git.postgresql.org/pg/commitdiff/b5fc98aedf513780b9b61c904cfcb87a7d02fbf1 Modified Files -- doc/src/sgml/release-7.4.sgml | 248 ++--- doc/src/sgml/release-8.0.sgml | 216 +-- doc/src/sgml/release-8.1.sgml | 192 - doc/src/sgml/release-8.2.sgml | 192 - doc/src/sgml/release-8.3.sgml | 192 - doc/src/sgml/release-8.4.sgml | 184 doc/src/sgml/release-9.0.sgml | 192 - doc/src/sgml/release-9.1.sgml | 200 - doc/src/sgml/release-9.2.sgml | 176 +++ doc/src/sgml/release-old.sgml | 488 +- 10 files changed, 1140 insertions(+), 1140 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: update markup for release note "release date" block
doc: update markup for release note "release date" block This has to be backpatched to all supported releases so release markup added to HEAD and copied to back branches matches the existing markup. Reported-by: Peter Eisentraut Discussion: 2b8a2552-fffa-f7c8-97c5-14db47a87...@2ndquadrant.com Author: initial patch and sample markup by Peter Eisentraut Backpatch-through: 9.2 Branch -- REL9_3_STABLE Details --- https://git.postgresql.org/pg/commitdiff/2c80c3710fd9bc98e06d65006bc89a8024430745 Modified Files -- doc/src/sgml/release-7.4.sgml | 248 ++--- doc/src/sgml/release-8.0.sgml | 216 +-- doc/src/sgml/release-8.1.sgml | 192 - doc/src/sgml/release-8.2.sgml | 192 - doc/src/sgml/release-8.3.sgml | 192 - doc/src/sgml/release-8.4.sgml | 184 doc/src/sgml/release-9.0.sgml | 192 - doc/src/sgml/release-9.1.sgml | 200 - doc/src/sgml/release-9.2.sgml | 176 +++ doc/src/sgml/release-9.3.sgml | 144 ++--- doc/src/sgml/release-old.sgml | 488 +- 11 files changed, 1212 insertions(+), 1212 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: update markup for release note "release date" block
doc: update markup for release note "release date" block This has to be backpatched to all supported releases so release markup added to HEAD and copied to back branches matches the existing markup. Reported-by: Peter Eisentraut Discussion: 2b8a2552-fffa-f7c8-97c5-14db47a87...@2ndquadrant.com Author: initial patch and sample markup by Peter Eisentraut Backpatch-through: 9.2 Branch -- REL9_5_STABLE Details --- https://git.postgresql.org/pg/commitdiff/73dc5f8ade5e2471a76e3a0857f753dd94b33426 Modified Files -- doc/src/sgml/release-7.4.sgml | 248 ++--- doc/src/sgml/release-8.0.sgml | 216 +-- doc/src/sgml/release-8.1.sgml | 192 - doc/src/sgml/release-8.2.sgml | 192 - doc/src/sgml/release-8.3.sgml | 192 - doc/src/sgml/release-8.4.sgml | 184 doc/src/sgml/release-9.0.sgml | 192 - doc/src/sgml/release-9.1.sgml | 200 - doc/src/sgml/release-9.2.sgml | 176 +++ doc/src/sgml/release-9.3.sgml | 144 ++--- doc/src/sgml/release-9.4.sgml | 104 - doc/src/sgml/release-9.5.sgml | 64 +++--- doc/src/sgml/release-old.sgml | 488 +- 13 files changed, 1296 insertions(+), 1296 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: update markup for release note "release date" block
doc: update markup for release note "release date" block This has to be backpatched to all supported releases so release markup added to HEAD and copied to back branches matches the existing markup. Reported-by: Peter Eisentraut Discussion: 2b8a2552-fffa-f7c8-97c5-14db47a87...@2ndquadrant.com Author: initial patch and sample markup by Peter Eisentraut Backpatch-through: 9.2 Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitdiff/610926e1d98121b7f9d3c175d5f8b2b75898b046 Modified Files -- doc/src/sgml/release-7.4.sgml | 248 ++--- doc/src/sgml/release-8.0.sgml | 216 +-- doc/src/sgml/release-8.1.sgml | 192 - doc/src/sgml/release-8.2.sgml | 192 - doc/src/sgml/release-8.3.sgml | 192 - doc/src/sgml/release-8.4.sgml | 184 doc/src/sgml/release-9.0.sgml | 192 - doc/src/sgml/release-9.1.sgml | 200 - doc/src/sgml/release-9.2.sgml | 176 +++ doc/src/sgml/release-9.3.sgml | 144 ++--- doc/src/sgml/release-9.4.sgml | 104 - doc/src/sgml/release-9.5.sgml | 64 +++--- doc/src/sgml/release-9.6.sgml | 32 +-- doc/src/sgml/release-old.sgml | 488 +- 14 files changed, 1312 insertions(+), 1312 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: update markup for release note "release date" block
doc: update markup for release note "release date" block This has to be backpatched to all supported releases so release markup added to HEAD and copied to back branches matches the existing markup. Reported-by: Peter Eisentraut Discussion: 2b8a2552-fffa-f7c8-97c5-14db47a87...@2ndquadrant.com Author: initial patch and sample markup by Peter Eisentraut Backpatch-through: 9.2 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/9ed74fd463ede1db4ce829f9ff461d0b7f28f1f3 Modified Files -- doc/src/sgml/release-10.sgml | 9 +- doc/src/sgml/release-7.4.sgml | 248 ++--- doc/src/sgml/release-8.0.sgml | 216 +-- doc/src/sgml/release-8.1.sgml | 192 - doc/src/sgml/release-8.2.sgml | 192 - doc/src/sgml/release-8.3.sgml | 192 - doc/src/sgml/release-8.4.sgml | 184 doc/src/sgml/release-9.0.sgml | 192 - doc/src/sgml/release-9.1.sgml | 200 - doc/src/sgml/release-9.2.sgml | 176 +++ doc/src/sgml/release-9.3.sgml | 144 ++--- doc/src/sgml/release-9.4.sgml | 104 - doc/src/sgml/release-9.5.sgml | 64 +++--- doc/src/sgml/release-9.6.sgml | 32 +-- doc/src/sgml/release-old.sgml | 488 +- 15 files changed, 1316 insertions(+), 1317 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: update markup for release note "release date" block
doc: update markup for release note "release date" block This has to be backpatched to all supported releases so release markup added to HEAD and copied to back branches matches the existing markup. Reported-by: Peter Eisentraut Discussion: 2b8a2552-fffa-f7c8-97c5-14db47a87...@2ndquadrant.com Author: initial patch and sample markup by Peter Eisentraut Backpatch-through: 9.2 Branch -- REL9_4_STABLE Details --- https://git.postgresql.org/pg/commitdiff/a9787e737dc8fa8779263c4112c25b7f0792556c Modified Files -- doc/src/sgml/release-7.4.sgml | 248 ++--- doc/src/sgml/release-8.0.sgml | 216 +-- doc/src/sgml/release-8.1.sgml | 192 - doc/src/sgml/release-8.2.sgml | 192 - doc/src/sgml/release-8.3.sgml | 192 - doc/src/sgml/release-8.4.sgml | 184 doc/src/sgml/release-9.0.sgml | 192 - doc/src/sgml/release-9.1.sgml | 200 - doc/src/sgml/release-9.2.sgml | 176 +++ doc/src/sgml/release-9.3.sgml | 144 ++--- doc/src/sgml/release-9.4.sgml | 104 - doc/src/sgml/release-old.sgml | 488 +- 12 files changed, 1264 insertions(+), 1264 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: pgindent: use HTTP instead of FTP to retrieve pg_bsd_indent src
pgindent: use HTTP instead of FTP to retrieve pg_bsd_indent src FTP support will be removed from ftp.postgresql.org in months, but http still works. Typedefs already used http. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/c4c493fd3581dfbce45e903b87e12eea508f47e4 Modified Files -- src/tools/pgindent/pgindent | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: add Simon Riggs to VACUUM VERBOSE PG 10 release note item
doc: add Simon Riggs to VACUUM VERBOSE PG 10 release note item Reported-by: Masahiko Sawada Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/74cadeaa2f12320c5064af61915fefcd5c24149a Modified Files -- doc/src/sgml/release-10.sgml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc PG 10: adjustments to BRIN, WAL, JSON, XML items, syntax
doc PG 10: adjustments to BRIN, WAL, JSON, XML items, syntax Reported-by: Alvaro Herrera Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/628462bda908873688ce738a191b470ab769d604 Modified Files -- doc/src/sgml/release-10.sgml | 145 +++ 1 file changed, 64 insertions(+), 81 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: update PG 10 release notes
doc: update PG 10 release notes Mention vacuum verbose includes oldest xmin, BRIN index usage estimation, and multi-column statistics. Reported-by: Masahiko Sawada, Alvaro Herrera Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/5469e44ffc2077cb8371686497022cb5afd1af87 Modified Files -- doc/src/sgml/release-10.sgml | 22 ++ 1 file changed, 18 insertions(+), 4 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: PG 10 release note updates for psql, GiST, and markup
doc: PG 10 release note updates for psql, GiST, and markup Reported-by: Andrew Borodin, Fabien COELHO, Dagfinn Ilmari Mannsaker Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/4f45beba7aea007cbae68eaea5d04d4cab7e4f62 Modified Files -- doc/src/sgml/release-10.sgml | 37 + 1 file changed, 17 insertions(+), 20 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: add missing closing 'sect3' tag for ICU patch
doc: add missing closing 'sect3' tag for ICU patch Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/218747d2cf3cc1536ff77435e596280e0e739760 Modified Files -- doc/src/sgml/charset.sgml | 1 + 1 file changed, 1 insertion(+) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: clarify that function "ownership" that controls permission
doc: clarify that function "ownership" that controls permission It used to say the creation user. Reported-by: Nathan Wagner Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/17fa3e834f288a2a8f0b3927d3f7f02451126686 Modified Files -- doc/src/sgml/ref/create_function.sgml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: adjust 'Infinity' example to include minus
doc: adjust 'Infinity' example to include minus This clarifies that quoted infinity values must have the negative signs inside single quotes. Reported-by: Don Morrison Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/692ed0567d0a17013b8bc631ad6cab29470a944d Modified Files -- doc/src/sgml/datatype.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: improve createdb example
doc: improve createdb example The previous example could error out due to encoding mismatches; use -T/template instead. Reported-by: Jason O'Donnell Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/c709b113e8f5433ea2a66b2fb08d9324dd596642 Modified Files -- doc/src/sgml/ref/createdb.sgml | 8 1 file changed, 4 insertions(+), 4 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Avoid having vacuum set reltuples to 0 on non-empty relations in
On Fri, Mar 17, 2017 at 10:00:17AM -0400, Tom Lane wrote: > Andrew Dunstan <andrew.duns...@2ndquadrant.com> writes: > > On 03/17/2017 09:30 AM, Robert Haas wrote: > >> In the department of nitpicks, we usually try to write commit messages > >> so that the first line is a summary line which stands alone, and then > >> there's a blank line, and then more follows. a la > >> https://chris.beams.io/posts/git-commit/#separate > > > Yeah, In our case email subjects seem to be truncated at 64 chars, so > > it's best to stay under that limit if possible - 50 chars is sometimes > > pretty limiting. > > FWIW, I usually try to keep line length in commit messages to <= 75 > characters, as that is the wrap boundary in "git log" output. It's > nice if the summary line can be made shorter, but it's often damn > hard to cram an adequate summary into 75 chars, let alone fewer. > > (Links to mailing-list threads must ignore the length limit, sadly.) Here are the length limits I have found, and I display this in my email editor when I am creating a commit message: -- email subject limit ----- -- gitweb summary limit -- -- Bruce Momjian <br...@momjian.us>http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: pg_upgrade docs: clarify instructions on standby extensions
On Sat, Feb 25, 2017 at 05:59:34PM +, Bruce Momjian wrote: > pg_upgrade docs: clarify instructions on standby extensions > > Previously the pg_upgrade standby upgrade instructions said not to > execute pgcrypto.sql, but it should have referenced the extension > command "CREATE EXTENSION pgcrypto". This patch makes that doc change. Just to clarify, the doc adjustment was made to the main pg_upgrade shared-object/extension handling instructions, not the standby instructions. Sorry. -- Bruce Momjian <br...@momjian.us>http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Add /config.cache to .gitignore in back branches
Add /config.cache to .gitignore in back branches For some reason config.cache was not being git-ignored in these back branches. Backpatch-through: 9.2 to 9.4 Branch -- REL9_2_STABLE Details --- http://git.postgresql.org/pg/commitdiff/3703cfead94a18d9eff5b89203244d650a1a791c Modified Files -- .gitignore | 1 + 1 file changed, 1 insertion(+) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Add /config.cache to .gitignore in back branches
Add /config.cache to .gitignore in back branches For some reason config.cache was not being git-ignored in these back branches. Backpatch-through: 9.2 to 9.4 Branch -- REL9_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff/1f0d78863eb88ca8ee9c3b5215d532900e722e57 Modified Files -- .gitignore | 1 + 1 file changed, 1 insertion(+) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Add /config.cache to .gitignore in back branches
Add /config.cache to .gitignore in back branches For some reason config.cache was not being git-ignored in these back branches. Backpatch-through: 9.2 to 9.4 Branch -- REL9_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/6987277619f218d4056178ac1d9c6d9ef8efc9c8 Modified Files -- .gitignore | 1 + 1 file changed, 1 insertion(+) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: pg_upgrade docs: clarify instructions on standby extensions
pg_upgrade docs: clarify instructions on standby extensions Previously the pg_upgrade standby upgrade instructions said not to execute pgcrypto.sql, but it should have referenced the extension command "CREATE EXTENSION pgcrypto". This patch makes that doc change. Reported-by: a private bug report Backpatch-through: 9.4, where standby instructions were added Branch -- REL9_5_STABLE Details --- http://git.postgresql.org/pg/commitdiff/3c6f766f68114785195cf50700c71021942e60a9 Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: pg_upgrade docs: clarify instructions on standby extensions
pg_upgrade docs: clarify instructions on standby extensions Previously the pg_upgrade standby upgrade instructions said not to execute pgcrypto.sql, but it should have referenced the extension command "CREATE EXTENSION pgcrypto". This patch makes that doc change. Reported-by: a private bug report Backpatch-through: 9.4, where standby instructions were added Branch -- REL9_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff/ddcfeba95e2cdb90b1f37ac5cae97124373fa076 Modified Files -- doc/src/sgml/pgupgrade.sgml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: pg_upgrade docs: clarify instructions on standby extensions
pg_upgrade docs: clarify instructions on standby extensions Previously the pg_upgrade standby upgrade instructions said not to execute pgcrypto.sql, but it should have referenced the extension command "CREATE EXTENSION pgcrypto". This patch makes that doc change. Reported-by: a private bug report Backpatch-through: 9.4, where standby instructions were added Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/5639ceddcb7f3efa8751b2ba6e50cc1d27cc2a45 Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: pg_upgrade docs: clarify instructions on standby extensions
pg_upgrade docs: clarify instructions on standby extensions Previously the pg_upgrade standby upgrade instructions said not to execute pgcrypto.sql, but it should have referenced the extension command "CREATE EXTENSION pgcrypto". This patch makes that doc change. Reported-by: a private bug report Backpatch-through: 9.4, where standby instructions were added Branch -- REL9_6_STABLE Details --- http://git.postgresql.org/pg/commitdiff/f97f4fc028ccc284683ba400a51d59e534901336 Modified Files -- doc/src/sgml/ref/pgupgrade.sgml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: pg_xlogdump: document --path behavior
pg_xlogdump: document --path behavior The previous --path documentation and --help output were wrong in both its meaning and the defaults. Reviewed-by: Michael Paquier Backpatch-through: 9.6 Branch -- REL9_6_STABLE Details --- http://git.postgresql.org/pg/commitdiff/1c15f843485bf36e279686b6ed0b659232b975bb Modified Files -- doc/src/sgml/ref/pg_xlogdump.sgml | 9 ++--- src/bin/pg_xlogdump/pg_xlogdump.c | 5 +++-- 2 files changed, 9 insertions(+), 5 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: pg_xlogdump: document --path behavior
pg_xlogdump: document --path behavior The previous --path documentation and --help output were wrong in both its meaning and the defaults. Reviewed-by: Michael Paquier Backpatch-through: 9.6 Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/73f8d7331343cefaaa97a0039421158fc8462c81 Modified Files -- doc/src/sgml/ref/pg_xlogdump.sgml | 9 ++--- src/bin/pg_xlogdump/pg_xlogdump.c | 5 +++-- 2 files changed, 9 insertions(+), 5 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Update copyright for 2017
On Wed, Jan 4, 2017 at 10:05:10AM -0500, Tom Lane wrote: > Andres Freund <and...@anarazel.de> writes: > > On 2017-01-03 13:02:28 -0500, Bruce Momjian wrote: > >> Yeah, I was doing parallel pulls of different branches in git via shell > >> script, and it seems the size of this commit showed me that doesn't > >> work. Sorry. > > > Shouldn't you check the results of something like this before pushing? > > Sorry for piling on, but that seems like a quite critical step. > > Actually, my takeaway from this was "don't ever use git reset on the repo". > "git revert" would have been much safer. Yeah, it would have meant that > git blame on the 9.2 branch would have some useless noise, but how much > does anyone still care about that? FYI, my takeaway is that you can't run parallel 'git pull' operations on different branches checked out of the same tree, at least as setup from instructions on our wiki. Such parallel operations generate messages indicating someone else is working on the tree, but I now realize those are _warnings_ and this behavior should be avoided. Normally it works fine, but for a big commit, it can move a changeset from one branch to another, with disastrous consequences. Yes, I should have checked more, but I often do a pull before a push as another check, so that can mess it up too. Basically, if your tools are being used improperly, checking can make things worse too. -- Bruce Momjian <br...@momjian.us>http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Update manual set of copyright files for 2017
Update manual set of copyright files for 2017 Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/60f1e514ad0db017bc583b0e15d056b777bd9626 Modified Files -- doc/src/sgml/legal.sgml | 2 +- src/interfaces/libpq/libpq.rc.in | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Update copyright for 2017
Update copyright for 2017 Backpatch-through: certain files through 9.2 Branch -- REL9_2_STABLE Details --- http://git.postgresql.org/pg/commitdiff/83a25a5209d93615e6d5f3eee4ef649853478498 Modified Files -- COPYRIGHT | 2 +- doc/src/sgml/legal.sgml | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Update copyright for 2017
On Tue, Jan 3, 2017 at 06:57:44PM +0100, Magnus Hagander wrote: > I'm leaning for +1 for resetting. It'll be a pain for any mirrors of the > repo, but I think the clean history is worth it. > > > > It seems bruce pushed a whole bunch of merge conflicts, and possibly more. I > think his commit sscripts are badly broken. > > I've pushed a reset to the master repo. Working on the mirror now. Yeah, I was doing parallel pulls of different branches in git via shell script, and it seems the size of this commit showed me that doesn't work. Sorry. -- Bruce Momjian <br...@momjian.us>http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Update copyright for 2017
On Tue, Jan 3, 2017 at 06:46:32PM +0100, Magnus Hagander wrote: > Is this a big enough boo that we actually want to reset the master repo to get > rid of it? > > If so, we need to do it *now* beore people get a chance to mirror it > properly.. > > Thoughts? > > If not, just a revert should work of course.. OK, not sure how this happened but I think it has to do with my accidentally doing a 'pull' after the changes, and doing multiple branches. Whatever you suggest is fine --- I will wait. --- > > //Magnus > > > On Tue, Jan 3, 2017 at 6:41 PM, Bruce Momjian <br...@momjian.us> wrote: > > > Sorry, this will be reverted and redone. > > > ------- > > On Tue, Jan 3, 2017 at 05:38:05PM +, Bruce Momjian wrote: > > Update copyright for 2017 > > > > Backpatch-through: certain files through 9.2 > > > > Branch > > -- > > REL9_2_STABLE > > > > Details > > --- > > http://git.postgresql.org/pg/commitdiff/19371e148207c33d15fded06a178d5 > 8d0781141d > > > > Modified Files > > -- > > COPYRIGHT | 2 +- > > configure | 11 + > > configure.in | 4 + > > contrib/adminpack/adminpack.c | 4 + > > contrib/auth_delay/auth_delay.c | 4 + > > contrib/auto_explain/auto_explain.c | 4 + > > contrib/bloom/blcost.c | 48 + > > contrib/bloom/blinsert.c | 358 ++ > > contrib/bloom/bloom.h | 212 + > > contrib/bloom/blscan.c | 173 + > > contrib/bloom/blutils.c | 485 ++ > > contrib/bloom/blvacuum.c | 217 + > > contrib/bloom/blvalidate.c | 220 + > > contrib/dblink/dblink.c | 4 + > > contrib/dblink/dblink.h | 4 + > > contrib/dict_int/dict_int.c | 4 + > > contrib/dict_xsyn/dict_xsyn.c | 4 + > > contrib/dummy_seclabel/dummy_seclabel.c | 4 + > > contrib/file_fdw/file_fdw.c | 4 + > > contrib/fuzzystrmatch/fuzzystrmatch.c | 4 + > > contrib/fuzzystrmatch/levenshtein.c | 4 + > > contrib/intarray/_int_selfuncs.c | 341 ++ > > contrib/isn/isn.c | 4 + > > contrib/isn/isn.h | 4 + > > contrib/pageinspect/brinfuncs.c | 409 ++ > > contrib/pageinspect/fsmfuncs.c | 4 + > > contrib/pageinspect/ginfuncs.c | 283 ++ > > contrib/pageinspect/heapfuncs.c | 4 + > > contrib/pageinspect/rawpage.c | 4 + > > contrib/passwordcheck/passwordcheck.c | 4 + > > contrib/pg_prewarm/pg_prewarm.c | 206 + > > contrib/pg_stat_statements/pg_stat_statements.c | 4 + > > contrib/pg_trgm/trgm_regexp.c | 2244 + > > contrib/pg_upgrade/check.c | 5 + > > contrib/pg_upgrade/controldata.c | 5 + > > contrib/pg_upgrade/exec.c | 5 + > > contrib/pg_upgrade/option.c | 5 + > > contrib/pg_upgrade/pg_upgrade.h | 5 + > > contrib/pg_upgrade/server.c | 5 + > > contrib/pg_upgrade/test.sh | 4 + > > contrib/pg_visibility/pg_visibility.c | 749 +++ > > contrib/pgstattuple/pgstatapprox.c | 303 ++ > > contrib/postgres_fdw/connection.c | 838 > > contrib/postgres_fdw/deparse.c | 2940 > > contrib/postgres_fdw/option.c | 363 ++ > > contrib/postgres_fdw/postgres_fdw.c | 5029 > > > contrib/postgres_fdw/postgres_fdw.h | 172 + > > contrib/postgres_fdw/shippable.c |
[COMMITTERS] pgsql: Update copyright for 2017
Update copyright for 2017 Backpatch-through: certain files through 9.2 Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/7090eed3b3e476d6ac20ba8e5f6e3914f18f9632 Modified Files -- COPYRIGHT | 2 +- doc/src/sgml/legal.sgml | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Update copyright for 2017
Sorry, this will be reverted and redone. --- On Tue, Jan 3, 2017 at 05:38:05PM +, Bruce Momjian wrote: > Update copyright for 2017 > > Backpatch-through: certain files through 9.2 > > Branch > -- > REL9_2_STABLE > > Details > --- > http://git.postgresql.org/pg/commitdiff/19371e148207c33d15fded06a178d58d0781141d > > Modified Files > -- > COPYRIGHT |2 +- > configure | 11 + > configure.in |4 + > contrib/adminpack/adminpack.c |4 + > contrib/auth_delay/auth_delay.c|4 + > contrib/auto_explain/auto_explain.c|4 + > contrib/bloom/blcost.c | 48 + > contrib/bloom/blinsert.c | 358 ++ > contrib/bloom/bloom.h | 212 + > contrib/bloom/blscan.c | 173 + > contrib/bloom/blutils.c| 485 ++ > contrib/bloom/blvacuum.c | 217 + > contrib/bloom/blvalidate.c | 220 + > contrib/dblink/dblink.c|4 + > contrib/dblink/dblink.h|4 + > contrib/dict_int/dict_int.c|4 + > contrib/dict_xsyn/dict_xsyn.c |4 + > contrib/dummy_seclabel/dummy_seclabel.c|4 + > contrib/file_fdw/file_fdw.c|4 + > contrib/fuzzystrmatch/fuzzystrmatch.c |4 + > contrib/fuzzystrmatch/levenshtein.c|4 + > contrib/intarray/_int_selfuncs.c | 341 ++ > contrib/isn/isn.c |4 + > contrib/isn/isn.h |4 + > contrib/pageinspect/brinfuncs.c| 409 ++ > contrib/pageinspect/fsmfuncs.c |4 + > contrib/pageinspect/ginfuncs.c | 283 ++ > contrib/pageinspect/heapfuncs.c|4 + > contrib/pageinspect/rawpage.c |4 + > contrib/passwordcheck/passwordcheck.c |4 + > contrib/pg_prewarm/pg_prewarm.c| 206 + > contrib/pg_stat_statements/pg_stat_statements.c|4 + > contrib/pg_trgm/trgm_regexp.c | 2244 + > contrib/pg_upgrade/check.c |5 + > contrib/pg_upgrade/controldata.c |5 + > contrib/pg_upgrade/exec.c |5 + > contrib/pg_upgrade/option.c|5 + > contrib/pg_upgrade/pg_upgrade.h|5 + > contrib/pg_upgrade/server.c|5 + > contrib/pg_upgrade/test.sh |4 + > contrib/pg_visibility/pg_visibility.c | 749 +++ > contrib/pgstattuple/pgstatapprox.c | 303 ++ > contrib/postgres_fdw/connection.c | 838 > contrib/postgres_fdw/deparse.c | 2940 > contrib/postgres_fdw/option.c | 363 ++ > contrib/postgres_fdw/postgres_fdw.c| 5029 > contrib/postgres_fdw/postgres_fdw.h| 172 + > contrib/postgres_fdw/shippable.c | 214 + > contrib/sepgsql/database.c |4 + > contrib/sepgsql/dml.c |4 + > contrib/sepgsql/hooks.c|4 + > contrib/sepgsql/label.c|4 + > contrib/sepgsql/launcher |4 + > contrib/sepgsql/proc.c |4 + > contrib/sepgsql/relation.c |4 + > contrib/sepgsql/schema.c |4 + > contrib/sepgsql/selinux.c |4 + > contrib/sepgsql/sepgsql.h |4 + > contrib/sepgsql/uavc.c |4 + > contrib/tablefunc/tablefunc.c |4 + > contrib/tablefunc/tablefunc.h |4 + > contrib/tcn/tcn.c |4 + > contrib/test_decoding/test_decoding.c | 489 ++ > contrib/test_parser/test_parser.c |4 + > contrib/tsearch2/tsearch2.c|4 + > contrib/tsm_system_rows/tsm_system_rows.c | 394 ++ > contrib/tsm_system_time/tsm_system_time.c | 358 ++ > contrib/unaccent/unaccent.c|4 + > contrib/uuid-ossp/uuid
[COMMITTERS] pgsql: Update copyright for 2017
Update copyright for 2017 Backpatch-through: certain files through 9.2 Branch -- REL9_2_STABLE Details --- http://git.postgresql.org/pg/commitdiff/19371e148207c33d15fded06a178d58d0781141d Modified Files -- COPYRIGHT |2 +- configure | 11 + configure.in |4 + contrib/adminpack/adminpack.c |4 + contrib/auth_delay/auth_delay.c|4 + contrib/auto_explain/auto_explain.c|4 + contrib/bloom/blcost.c | 48 + contrib/bloom/blinsert.c | 358 ++ contrib/bloom/bloom.h | 212 + contrib/bloom/blscan.c | 173 + contrib/bloom/blutils.c| 485 ++ contrib/bloom/blvacuum.c | 217 + contrib/bloom/blvalidate.c | 220 + contrib/dblink/dblink.c|4 + contrib/dblink/dblink.h|4 + contrib/dict_int/dict_int.c|4 + contrib/dict_xsyn/dict_xsyn.c |4 + contrib/dummy_seclabel/dummy_seclabel.c|4 + contrib/file_fdw/file_fdw.c|4 + contrib/fuzzystrmatch/fuzzystrmatch.c |4 + contrib/fuzzystrmatch/levenshtein.c|4 + contrib/intarray/_int_selfuncs.c | 341 ++ contrib/isn/isn.c |4 + contrib/isn/isn.h |4 + contrib/pageinspect/brinfuncs.c| 409 ++ contrib/pageinspect/fsmfuncs.c |4 + contrib/pageinspect/ginfuncs.c | 283 ++ contrib/pageinspect/heapfuncs.c|4 + contrib/pageinspect/rawpage.c |4 + contrib/passwordcheck/passwordcheck.c |4 + contrib/pg_prewarm/pg_prewarm.c| 206 + contrib/pg_stat_statements/pg_stat_statements.c|4 + contrib/pg_trgm/trgm_regexp.c | 2244 + contrib/pg_upgrade/check.c |5 + contrib/pg_upgrade/controldata.c |5 + contrib/pg_upgrade/exec.c |5 + contrib/pg_upgrade/option.c|5 + contrib/pg_upgrade/pg_upgrade.h|5 + contrib/pg_upgrade/server.c|5 + contrib/pg_upgrade/test.sh |4 + contrib/pg_visibility/pg_visibility.c | 749 +++ contrib/pgstattuple/pgstatapprox.c | 303 ++ contrib/postgres_fdw/connection.c | 838 contrib/postgres_fdw/deparse.c | 2940 contrib/postgres_fdw/option.c | 363 ++ contrib/postgres_fdw/postgres_fdw.c| 5029 contrib/postgres_fdw/postgres_fdw.h| 172 + contrib/postgres_fdw/shippable.c | 214 + contrib/sepgsql/database.c |4 + contrib/sepgsql/dml.c |4 + contrib/sepgsql/hooks.c|4 + contrib/sepgsql/label.c|4 + contrib/sepgsql/launcher |4 + contrib/sepgsql/proc.c |4 + contrib/sepgsql/relation.c |4 + contrib/sepgsql/schema.c |4 + contrib/sepgsql/selinux.c |4 + contrib/sepgsql/sepgsql.h |4 + contrib/sepgsql/uavc.c |4 + contrib/tablefunc/tablefunc.c |4 + contrib/tablefunc/tablefunc.h |4 + contrib/tcn/tcn.c |4 + contrib/test_decoding/test_decoding.c | 489 ++ contrib/test_parser/test_parser.c |4 + contrib/tsearch2/tsearch2.c|4 + contrib/tsm_system_rows/tsm_system_rows.c | 394 ++ contrib/tsm_system_time/tsm_system_time.c | 358 ++ contrib/unaccent/unaccent.c|4 + contrib/uuid-ossp/uuid-ossp.c |6 + contrib/vacuumlo/vacuumlo.c|4 + doc/src/sgml/generate-errcodes-table.pl|4 + doc/src/sgml/legal.sgml|9 +- doc/src/sgml/lobj.sgml |9 + src/backend/Makefile |4 + src/backend/access/brin/brin.c | 1227 + src/backend/access/brin/brin_inclusion.c | 702 +++ src/backend/access/brin/brin_minmax.c | 374 ++ src/backend/access/brin/brin_pageops.c | 893
[COMMITTERS] pgsql: Update copyright for 2017
Update copyright for 2017 Backpatch-through: certain files through 9.2 Branch -- REL9_6_STABLE Details --- http://git.postgresql.org/pg/commitdiff/344ae600ac036675d52afca9e8b363628d78d36d Modified Files -- COPYRIGHT | 2 +- doc/src/sgml/legal.sgml | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Update copyright for 2017
Update copyright for 2017 Backpatch-through: certain files through 9.2 Branch -- REL9_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff/1dfe7f068121d15d59c85ecd936d154922e195d1 Modified Files -- COPYRIGHT | 2 +- doc/src/sgml/legal.sgml | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Update copyright for 2017
Update copyright for 2017 Backpatch-through: certain files through 9.2 Branch -- REL9_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/e7c586e7b222b80c42de473468ce5e7e14bbca60 Modified Files -- COPYRIGHT | 2 +- doc/src/sgml/legal.sgml | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Update copyright for 2017
Update copyright for 2017 Backpatch-through: certain files through 9.2 Branch -- REL9_5_STABLE Details --- http://git.postgresql.org/pg/commitdiff/92ade06b2cf3985a93f45edd10d4855dcc0bf26d Modified Files -- COPYRIGHT | 2 +- doc/src/sgml/legal.sgml | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Properly indent postgresql.conf comments to align
On Thu, Oct 27, 2016 at 08:37:59AM -0400, Bruce Momjian wrote: > > I suggest that the best way out of this might be to detab > > postgresql.conf.sample entirely, and ditto for our other sample > > config files. We could probably set up .gitattributes to make > > git complain if anyone re-introduces tabs into those files. > > Uh, the postgresql.conf file is full of tabs, and they all assume > 8-space tabs. I was just making those few lines consistent. > > Not sure we want to remove all tabs though. One advantage of using tabs in postgresql.conf is that you can add/remove comment markers on a key/value line, or add a few characters, without causing the end-of-line comment to shift. -- Bruce Momjian <br...@momjian.us>http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Properly indent postgresql.conf comments to align
On Wed, Oct 26, 2016 at 10:23:56PM -0400, Tom Lane wrote: > Bruce Momjian <br...@momjian.us> writes: > > Properly indent postgresql.conf comments to align > > I think "properly" here is very dependent on what you believe the > tab width is. While most of us have our editors set up for 4-space > tabs in C files, I don't think all contributors do so for text files > (I don't, for one). And the odds that the average user will be set up > to edit postgresql.conf with 4-space tabs are nil. > > I suggest that the best way out of this might be to detab > postgresql.conf.sample entirely, and ditto for our other sample > config files. We could probably set up .gitattributes to make > git complain if anyone re-introduces tabs into those files. Uh, the postgresql.conf file is full of tabs, and they all assume 8-space tabs. I was just making those few lines consistent. Not sure we want to remove all tabs though. -- Bruce Momjian <br...@momjian.us>http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Properly indent postgresql.conf comments to align
Properly indent postgresql.conf comments to align A few comments were misaligned. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/586a46c22cea1526995195283fee0521fc6674b8 Modified Files -- src/backend/utils/misc/postgresql.conf.sample | 8 1 file changed, 4 insertions(+), 4 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Consistently mention 'SELECT pg_reload_conf()' in config files
Consistently mention 'SELECT pg_reload_conf()' in config files Previously we only mentioned SIGHUP and 'pg_ctl reload' in postgresql.conf and pg_hba.conf. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/10c064ce4dad088ba2d8b978bff6009b9f22dc3a Modified Files -- src/backend/libpq/pg_hba.conf.sample | 10 +- src/backend/utils/misc/postgresql.conf.sample | 6 +++--- 2 files changed, 8 insertions(+), 8 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: C comment: fix function header comment
C comment: fix function header comment Fix for transformOnConflictClause(). Author: Tomonari Katsumata Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/1ff0042165cf835d1b6a2ab2c3b84c201eb6577b Modified Files -- src/backend/parser/analyze.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: 9.6 release notes: correct summary item about freeze
9.6 release notes: correct summary item about freeze Previously it less precisely talked about autovacuum. Backpatch-through: 9.6 Branch -- REL9_6_STABLE Details --- http://git.postgresql.org/pg/commitdiff/5c8cb8c01f0a8d484de301f58e673ed9c732fbbe Modified Files -- doc/src/sgml/release-9.6.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: 9.6 release notes: correct summary item about freeze
9.6 release notes: correct summary item about freeze Previously it less precisely talked about autovacuum. Backpatch-through: 9.6 Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/c9cf432ef32a9d29323b9b079178c1a6be126ff8 Modified Files -- doc/src/sgml/release-9.6.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: C comment: fix file name mention on line 1
C comment: fix file name mention on line 1 Author: Amit Langote Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/67e1e2aaff109c507da013c66009f048dda96f3e Modified Files -- src/include/libpq/libpq-be.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
