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
Modifi
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
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
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
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/ba01ef267ee48e86566886376c
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/d61f5bb7c444255b064a60df782907f7d
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
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
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
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
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 +++---
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 +++---
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
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 +++---
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.c0e592c5af4e
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.c0e592c5af4e
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.c0e592c5af4e
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.c0e592c5af4e
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
---
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
---
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
---
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
---
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
Detail
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
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
---
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
---
ht
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 http://momjian.us
EnterpriseDB http://enterprisedb.com
+ A
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 upg
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 upg
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 upg
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 upg
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 upg
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 upg
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 fd376afc9863dd8ea3eba95edfa79961
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 m
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 m
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 m
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 m
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 m
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
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
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
(+), 13 deletions(-)
>
>
> --
> 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 http://momjian.us
EnterpriseDB
On Tue, Jun 13, 2017 at 03:10:16PM -0400, Tom Lane wrote:
> Bruce Momjian 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
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 writes:
> > > > Uh, is there a reason this is only an Assert(), mea
On Tue, Jun 13, 2017 at 01:39:34PM -0400, Tom Lane wrote:
> Bruce Momjian 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&
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 http://momjia
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 de
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
-
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 | 1
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
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 fil
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 pgs
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(-)
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,
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
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
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
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
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
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
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/c4c493fd3581dfbce45e903b87e12eea508f47e
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,
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 +++--
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/5469e44ffc2077cb8371686497022cb5afd1
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/relea
doc: PG10 release note typo fix
Reported-by: daniel.westermann
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/a311d2a04f849f76d33b59995097999a311a4c62
Modified Files
--
doc/src/sgml/release-10.sgml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions
doc PG10rel: adjust hash index commits and add parallel subquery
Reported-by: Amit Kapila
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/f8ab08ad0e411139060bf943fa9931f7fbe97cde
Modified Files
--
doc/src/sgml/release-10.sgml | 18 ++
1 f
doc PG10: add commit for transition table item
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/fda4fec578505a624e4c0f0244816ae5bc10a3d1
Modified Files
--
doc/src/sgml/release-10.sgml | 2 ++
1 file changed, 2 insertions(+)
--
Sent via pgsql-committers
doc PG10: add Rafia Sabih to parallel index scan item
Reported-by: Amit Kapila
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/309191f66a947c5b63dd348a13aafa52b5847f94
Modified Files
--
doc/src/sgml/release-10.sgml | 2 +-
1 file changed, 1 insertion(+)
doc PG10: update EXPLAIN SUMMARY item
Reported-by: Tels
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/5f2b48d1dd17156c2021f9fa7c85d5c550bc2c6a
Modified Files
--
doc/src/sgml/release-10.sgml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
-
doc: update PG 10 item about referencing many relations
Reported-by: Tom Lane
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/ef0ba572b6e163328a2292bf9d6de7c919bd7cdd
Modified Files
--
doc/src/sgml/release-10.sgml | 4 ++--
1 file changed, 2 insertions(
doc: add PG 10 doc item about VACUUM truncation, 7e26e02ee
Reported-by: Andres Freund
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/3d7741194a4688adea8404ab0a7bb57bac20232b
Modified Files
--
doc/src/sgml/release-10.sgml | 16
1 file c
doc PG10: add commit 090010f2e and adjust EXPLAIN SUMMARY item
Reported-by: Tels, Andres Freund
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/3640cf5e1c8a0ae6ac55bf6384de0521dc77facf
Modified Files
--
doc/src/sgml/release-10.sgml | 19 +++
doc: properly indent SGML tags in PG 10 release notes
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/bf368fbee2a9ff1139b9331f025986ba68b8922a
Modified Files
--
doc/src/sgml/release-10.sgml | 5292 ++
1 file change
doc: PG 10 release notes updates
Reported-by: Michael Paquier, Felix Gerzaguet
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/cdd5bcad5ea6a2409e38e5c6e11e9901dae2d946
Modified Files
--
doc/src/sgml/release-10.sgml | 43 ++--
doc: PG 10 release note updates
Reported-by: David Rowley, Amit Langote, Ashutosh Bapat
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/64f0f7cfc75d92910cadb07dbcce3844eec79c36
Modified Files
--
doc/src/sgml/release-10.sgml | 27 ++-
doc: move hash info to new section and split out growth item
Reported-by: Amit Kapila
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/45e3d8ae2b1d16f6e6453089424e9c3346fa35f8
Modified Files
--
doc/src/sgml/release-10.sgml | 124 +
doc: move hash performance item into index section
The requirement to rebuild pg_upgrade-ed hash indexes was kept in the
incompatibilities section.
Reported-by: Amit Kapila
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/cef5dbbf2b8d8a5e7b536bcbf6d9066588c6173b
M
doc: add Rafia Sabih to PG 10 release note item
Reported-by: Amit Kapila
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/b007b1af20c3b276d5804b11dc3e471c8045480b
Modified Files
--
doc/src/sgml/release-10.sgml | 4 ++--
1 file changed, 2 insertions(+), 2
doc: fix PG 10 release note doc markup
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/d103e6718bfe4a1f50eb25b94db2cf9f84c69766
Modified Files
--
doc/src/sgml/release-10.sgml | 6 --
1 file changed, 6 deletions(-)
--
Sent via pgsql-committers mail
doc: merge PG 10 release SysV item
Reported-by: Takayuki Tsunakawa
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/419a055454dd234b78925e605582caf0def51ecb
Modified Files
--
doc/src/sgml/release-10.sgml | 2 --
1 file changed, 2 deletions(-)
--
Sent
doc: PG 10 fixes
Reported-by: Takayuki Tsunakawa
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/6e033c6a9639078501ac1830676ae062ee8a4aca
Modified Files
--
doc/src/sgml/release-10.sgml | 15 ++-
1 file changed, 2 insertions(+), 13 deletions(
doc: several minor PG 10 doc adjustments
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/bba375eb9df037c73af3743521f2b44e6fdf8c3b
Modified Files
--
doc/src/sgml/release-10.sgml | 69 ++--
1 file changed, 35 inserti
doc: fix attribution of sequence item, order incompatibilities
Reported-by: Andreas Karlsson
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/a0d932b39da7d7445dfc8da1e9979dd5cf4ea0a1
Modified Files
--
doc/src/sgml/release-10.sgml | 150 +
doc: first draft of Postgres 10 release notes
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/1d8573ed5569c014b9fd32e42248e58c7c28386d
Modified Files
--
doc/src/sgml/filelist.sgml |1 +
doc/src/sgml/ref/create_table.sgml |2 +-
doc/src/sgm
doc: update release doc markup instructions
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/66fade8a0447093e6bd5a39ee6fec38790479664
Modified Files
--
doc/src/sgml/release.sgml | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
--
Sent via pgs
On Thu, Apr 13, 2017 at 08:14:55PM +0300, Heikki Linnakangas wrote:
> On 04/13/2017 08:13 PM, Bruce Momjian wrote:
> >doc: add missing sect1 close tag
> >
> >Fixes commit 4f3b87ab780b95c2cc8a591259baefaff4852037
>
> Oops. Thanks for cleaning up after me! Michael pointe
doc: add missing sect1 close tag
Fixes commit 4f3b87ab780b95c2cc8a591259baefaff4852037
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/885fea5a34b036983379688d707b2a20735ebe4a
Modified Files
--
doc/src/sgml/protocol.sgml | 2 +-
1 file changed, 1 insertio
docs: update major release instructions
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/06fc54cd4355caf8e271ffc864885ccaa879159e
Modified Files
--
src/tools/RELEASE_CHANGES | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
--
Sent vi
git_changelog: improve comment
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/e1c86a55762c81ffbcf3985f7eb711026d40824f
Modified Files
--
src/tools/git_changelog | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Sent via pgsql-committers mailing
git_changelog: improve instructions for finding branch commits
Specifically, use '--summary' with 'git show'.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/854854019a282b6e74f586a3ee8c88c791193d32
Modified Files
--
src/tools/git_changelog | 2 +-
1 fil
doc: clearify pg_upgrade default copy behavior
Reported-by: Marek
Discussion: 20170328110253.2695.62...@wrigleys.postgresql.org
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/1e298b8dbb3220a0d5e073e0ad6a8afd35042c2a
Modified Files
--
doc/src/sgml/ref/
docs: Improve window function docs
Specifically, the behavior of general-purpose and statistical aggregates
as window functions was not clearly documented, and terms were
inconsistently used. Also add docs about the difference between
cume_dist and percent_rank, rather than just the formulas.
D
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 m
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/cre
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
Modifie
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
--
rd 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 ---
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 &q
1 - 100 of 8512 matches
Mail list logo
