Re: pgsql: Add allow_alter_system GUC.

On Fri, Mar 29, 2024 at 08:47:18AM -0400, Robert Haas wrote: > Oh no! Jelte, I'm so sorry ... I spelled your name wrong in this > commit message. :-( > > Please accept my apologies. I have made a record of this so I will make sure it is accurate in the release notes. -- B

pgsql: doc: fix CREATE ROLE typo

doc: fix CREATE ROLE typo This wording typo was added in PG 16. Reported-by: s.bai...@chorusintel.com Discussion: https://postgr.es/m/171150077554.7105.801523271545956...@wrigleys.postgresql.org Backpatch-through: 16 Branch -- master Details ---

pgsql: doc: fix CREATE ROLE typo

doc: fix CREATE ROLE typo This wording typo was added in PG 16. Reported-by: s.bai...@chorusintel.com Discussion: https://postgr.es/m/171150077554.7105.801523271545956...@wrigleys.postgresql.org Backpatch-through: 16 Branch -- REL_16_STABLE Details ---

pgsql: C comment: mention no doc for negative start of substring(text)

C comment: mention no doc for negative start of substring(text) Also add URL to hackers discussion. Backpatch-through: master Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/e648e77e25708874196326b6e4da30e7717156ab Modified Files --

pgsql: doc: add missing word "the"

doc: add missing word "the" Reported-by: dough...@gmail.com Discussion: https://postgr.es/m/170993253510.640.5664117187431542...@wrigleys.postgresql.org Backpatch-through: 12 Branch -- REL_14_STABLE Details ---

pgsql: doc: add missing word "the"

doc: add missing word "the" Reported-by: dough...@gmail.com Discussion: https://postgr.es/m/170993253510.640.5664117187431542...@wrigleys.postgresql.org Backpatch-through: 12 Branch -- master Details ---

pgsql: doc: add missing word "the"

doc: add missing word "the" Reported-by: dough...@gmail.com Discussion: https://postgr.es/m/170993253510.640.5664117187431542...@wrigleys.postgresql.org Backpatch-through: 12 Branch -- REL_13_STABLE Details ---

pgsql: doc: add missing word "the"

doc: add missing word "the" Reported-by: dough...@gmail.com Discussion: https://postgr.es/m/170993253510.640.5664117187431542...@wrigleys.postgresql.org Backpatch-through: 12 Branch -- REL_15_STABLE Details ---

pgsql: doc: add missing word "the"

doc: add missing word "the" Reported-by: dough...@gmail.com Discussion: https://postgr.es/m/170993253510.640.5664117187431542...@wrigleys.postgresql.org Backpatch-through: 12 Branch -- REL_12_STABLE Details ---

pgsql: doc: add missing word "the"

doc: add missing word "the" Reported-by: dough...@gmail.com Discussion: https://postgr.es/m/170993253510.640.5664117187431542...@wrigleys.postgresql.org Backpatch-through: 12 Branch -- REL_16_STABLE Details ---

pgsql: doc: improve role option documentation

doc: improve role option documentation Role option management was changed in Postgres 16. This patch improves the docs around these changes, including CREATE ROLE's INHERIT option, inheritance handling, and grant's ability to change role options. Discussion:

pgsql: doc: improve role option documentation

doc: improve role option documentation Role option management was changed in Postgres 16. This patch improves the docs around these changes, including CREATE ROLE's INHERIT option, inheritance handling, and grant's ability to change role options. Discussion:

pgsql: doc: clarify who owns the initdb-created cluster, by default

doc: clarify who owns the initdb-created cluster, by default Discussion: https://postgr.es/m/zzotbsdkebg_h...@momjian.us Backpatch-through: 16 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/5b2da240e01ecaef8181b0feebaeb69e6fefdaa0 Modified Files --

pgsql: doc: clarify who owns the initdb-created cluster, by default

doc: clarify who owns the initdb-created cluster, by default Discussion: https://postgr.es/m/zzotbsdkebg_h...@momjian.us Backpatch-through: 16 Branch -- REL_16_STABLE Details --- https://git.postgresql.org/pg/commitdiff/65ee2ed0d0da6dd45853b050b4d59634d64479bd Modified Files

pgsql: Update copyright for 2024

Update copyright for 2024 Reported-by: Michael Paquier Discussion: https://postgr.es/m/zzktdpxbbmt3c...@paquier.xyz Backpatch-through: 12 Branch -- REL_16_STABLE Details --- https://git.postgresql.org/pg/commitdiff/79a2af3e7277122858da61eff8177d5fe487ce92 Modified Files

pgsql: Update copyright for 2024

Update copyright for 2024 Reported-by: Michael Paquier Discussion: https://postgr.es/m/zzktdpxbbmt3c...@paquier.xyz Backpatch-through: 12 Branch -- REL_13_STABLE Details --- https://git.postgresql.org/pg/commitdiff/42afeae7b6db06c04ee5de7226b6b86e41b11da2 Modified Files

pgsql: Update copyright for 2024

Update copyright for 2024 Reported-by: Michael Paquier Discussion: https://postgr.es/m/zzktdpxbbmt3c...@paquier.xyz Backpatch-through: 12 Branch -- REL_12_STABLE Details --- https://git.postgresql.org/pg/commitdiff/49fa18390cfbd03956a4820910777c3d6585d5a7 Modified Files

pgsql: Update copyright for 2024

Update copyright for 2024 Reported-by: Michael Paquier Discussion: https://postgr.es/m/zzktdpxbbmt3c...@paquier.xyz Backpatch-through: 12 Branch -- REL_14_STABLE Details --- https://git.postgresql.org/pg/commitdiff/727cf6f6d31cf5a8cbe144207f22d0b76583f4d0 Modified Files

pgsql: Update copyright for 2024

Update copyright for 2024 Reported-by: Michael Paquier Discussion: https://postgr.es/m/zzktdpxbbmt3c...@paquier.xyz Backpatch-through: 12 Branch -- REL_15_STABLE Details --- https://git.postgresql.org/pg/commitdiff/596eeb10972b30d3c3d6f8368b33378837bcd261 Modified Files

pgsql: doc: add ISO 8601 extended format example using to_char()

doc: add ISO 8601 extended format example using to_char() Reported-by: juha.musto...@iki.fi Discussion: https://postgr.es/m/20170217160154.6101.52...@wrigleys.postgresql.org Co-authored-by: Erik Wienhold Backpatch-through: master Branch -- master Details ---

pgsql: doc: clarify handling of ON CONFLICT with triggers

doc: clarify handling of ON CONFLICT with triggers The previous wording was confusing. Also move partitioning mention to a more logical location. Reported-by: n...@fairwindsoft.com Discussion: https://postgr.es/m/20170703200710.27956.64...@wrigleys.postgresql.org Backpatch-through: master

pgsql: doc, pg_upgrade: add vacuumdb w/ tips for generating quick stats

doc, pg_upgrade: add vacuumdb w/ tips for generating quick stats Reported-by: Magnus Hagander Discussion: https://postgr.es/m/cabuevewgby-w7ektbjmy1rc+mmrl3fmrnx6yaukcr+7o9ps...@mail.gmail.com Backpatch-through: master Branch -- master Details ---

pgsql: doc: FOR UPDATE / KEY / SHARE / KEY SHARE takes an table alias

doc: FOR UPDATE / KEY / SHARE / KEY SHARE takes an table alias Previously only a table name was documented for this SELECT clause. Reported-by: robert Discussion: https://postgr.es/m/152483686904.19805.3369061025704720...@wrigleys.postgresql.org Backpatch-through: master Branch --

pgsql: doc, intagg: fix one-to-many mention to many-to-many

doc, intagg: fix one-to-many mention to many-to-many Reported-by: Christophe Courtois Discussion: https://postgr.es/m/aa7cfd73-0d8d-596a-b684-39faa479a...@dalibo.com Author: Christophe Courtois Backpatch-through: master Branch -- master Details ---

Re: pgsql: Doc: un-break PDF build.

On Sat, Nov 25, 2023 at 02:18:43PM -0500, Bruce Momjian wrote: > I showed it previously in this thread: > > $ make postgres-A4.pdf 2>&1 | grep -v INFO > /usr/bin/xsltproc --nonet --path . --path . --stringparam pg.version > '17devel' --stringparam img.src.p

Re: pgsql: Doc: un-break PDF build.

On Sat, Nov 25, 2023 at 02:14:11PM -0500, Andrew Dunstan wrote: > > On 2023-11-25 Sa 11:34, Bruce Momjian wrote: > > On Sat, Nov 25, 2023 at 11:26:16AM -0500, Tom Lane wrote: > > > Bruce Momjian writes: > > > > On Sat, Nov 25, 2023 at 10:50:10AM -0500, Tom Lan

Re: pgsql: Doc: un-break PDF build.

On Sat, Nov 25, 2023 at 11:26:16AM -0500, Tom Lane wrote: > Bruce Momjian writes: > > On Sat, Nov 25, 2023 at 10:50:10AM -0500, Tom Lane wrote: > >> Yeah, for some reason it only shows up when building PDFs. > >> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=

Re: pgsql: Doc: un-break PDF build.

On Sat, Nov 25, 2023 at 10:50:10AM -0500, Tom Lane wrote: > Bruce Momjian writes: > > Can someone tell me how you saw that warning in the build farm? I don't > > see it in with a make check or a build of the docs. > > Yeah, for some reason it only shows up when buil

Re: [COMMITTERS] pgsql: Move pg_test_fsync from contrib/ to src/bin/

of a shape similar to the other files. Now > there is only that: > /* > *pg_test_fsync.c > *tests all supported fsync() methods > */ > An idea what this gives as a patch is attached. This patch is old but the header is still missing, so patch applied to master.

pgsql: C comment: add header to pg_test_fsync.c

C comment: add header to pg_test_fsync.c Reported-by: Michael Paquier Discussion: https://postgr.es/m/cab7npqt1c9wruw4+esgf_-ru7erboc50a4r3ts1s-yt4oay...@mail.gmail.com Author: Michael Paquier Backpatch-through: master Branch -- master Details ---

pgsql: C comment: clarify that WAL files can be _recycled_ or removed

C comment: clarify that WAL files can be _recycled_ or removed Reported-by: Michael Paquier Discussion: https://postgr.es/m/cab7npqsddf0heotqu3gsepgqx+9c+6kjld3r6anyh7kkfdd...@mail.gmail.com Author: Michael Paquier Backpatch-through: master Branch -- master Details ---

Re: pgsql: Doc: un-break PDF build.

On Fri, Nov 24, 2023 at 08:16:12PM -0500, Bruce Momjian wrote: > > Thanks, I missed that issue. Can someone tell me how you saw that warning in the build farm? I don't see it in with a make check or a build of the docs. Attached is the patch that

pgsql: Use SECS_PER_HOUR macro in tzparser.c, instead of constants

Use SECS_PER_HOUR macro in tzparser.c, instead of constants Reported-by: CharSyam Discussion: https://postgr.es/m/camrlse5j_awfobdmrsvk14obksy+-2cjznnh_fciira7kwo...@mail.gmail.com Author: CharSyam Backpatch-through: master Branch -- master Details ---

pgsql: doc: gin_page_opaque_info() must be a _compressed_ GIN page

doc: gin_page_opaque_info() must be a _compressed_ GIN page Reported-by: Jeff Janes Discussion: https://postgr.es/m/CAMkU=1xvzqxtaiynm2pwj6snmtph3u3ammbwss7mvashs2o...@mail.gmail.com Author: Jeff Janes Backpatch-through: master Branch -- master Details ---

Re: pgsql: Doc: un-break PDF build.

er buildfarm. > > Branch > -- > master > > Details > --- > https://git.postgresql.org/pg/commitdiff/798394c6ccdada517c3508047a865d9994bfe25f > > Modified Files > -- > doc/src/sgml/gin.sgml | 2 +- > 1 file changed, 1 insertion(+), 1

pgsql: doc: improve ALTER TABLE "offical constraint" wording

doc: improve ALTER TABLE "offical constraint" wording Reported-by: Josh Kupershmidt Discussion: https://postgr.es/m/CAK3UJRF=KY_nx_TRQq+t6jOrtS2rry79ktkzPiMDhFx_K=d...@mail.gmail.com Author: Josh Kupershmidt Backpatch-through: master Branch -- master Details ---

pgsql: modify segno. for pg_walfile_name() and pg_walfile_name_offset()

modify segno. for pg_walfile_name() and pg_walfile_name_offset() Previously these functions returned the previous segment number if the LSN was on a segment boundary. We now always return the current segment number for an LSN. Docs updated to reflect this change. Regression tests added, author

pgsql: doc: remove documentation for deprecated @@@ operator

doc: remove documentation for deprecated @@@ operator Reported-by: Kyotaro HORIGUCHI Discussion: https://postgr.es/m/caf4au4wmuszrvhr+yspvabrfb_1d1fnrpy9trako2debi4c...@mail.gmail.com Co-authored-by: Oleg Bartunov Backpatch-through: master Branch -- master Details ---

pgsql: doc: mention vacuum's removal of commit timestamp information

doc: mention vacuum's removal of commit timestamp information Reported-by: Kyotaro HORIGUCHI Discussion: https://postgr.es/m/20180622.172132.230342845.horiguchi.kyot...@lab.ntt.co.jp Co-authored-by: Kyotaro HORIGUCHI Backpatch-through: 16 Branch -- REL_16_STABLE Details ---

pgsql: doc: mention vacuum's removal of commit timestamp information

doc: mention vacuum's removal of commit timestamp information Reported-by: Kyotaro HORIGUCHI Discussion: https://postgr.es/m/20180622.172132.230342845.horiguchi.kyot...@lab.ntt.co.jp Co-authored-by: Kyotaro HORIGUCHI Backpatch-through: 16 Branch -- master Details ---

pgsql: doc: add docs for age(xid) and mxid_age(xid)

doc: add docs for age(xid) and mxid_age(xid) Reported-by: David Rowley Discussion: https://postgr.es/m/CAKJS1f_OQpz7rpe-KJmskVxbU06buiXbfonxG3JLB+nGCJ5E=g...@mail.gmail.com Backpatch-through: 16 Branch -- master Details ---

pgsql: doc: add docs for age(xid) and mxid_age(xid)

doc: add docs for age(xid) and mxid_age(xid) Reported-by: David Rowley Discussion: https://postgr.es/m/CAKJS1f_OQpz7rpe-KJmskVxbU06buiXbfonxG3JLB+nGCJ5E=g...@mail.gmail.com Backpatch-through: 16 Branch -- REL_16_STABLE Details ---

pgsql: C comment: fix typos with unnecessary apostrophes

C comment: fix typos with unnecessary apostrophes Reported-by: Vinayak Pokale Discussion: https://postgr.es/m/CAEySZvh7gPTOqMhuKOBXEt=qf_1bcvfqb4maj4yatpjhxgx...@mail.gmail.com Author: Vinayak Pokale Backpatch-through: master Branch -- master Details ---

pgsql: doc: remove double-negative in REFRESH MATERIALIZED ... CONCURR

doc: remove double-negative in REFRESH MATERIALIZED ... CONCURR Reported-by: a...@robillo.net Discussion: https://postgr.es/m/20170208152743.1411.6...@wrigleys.postgresql.org Backpatch-through: master Branch -- master Details ---

pgsql: doc: FreeBSD uses camcontrol identify, not atacontrol, for cache

doc: FreeBSD uses camcontrol identify, not atacontrol, for cache This is for IDE drive cache control, same as SCSI (already documented properly). Reported-by: John Ekins Discussion: https://postgr.es/m/20170808224017.8424.69...@wrigleys.postgresql.org Author: John Ekins Backpatch-through: 12

pgsql: doc: FreeBSD uses camcontrol identify, not atacontrol, for cache

doc: FreeBSD uses camcontrol identify, not atacontrol, for cache This is for IDE drive cache control, same as SCSI (already documented properly). Reported-by: John Ekins Discussion: https://postgr.es/m/20170808224017.8424.69...@wrigleys.postgresql.org Author: John Ekins Backpatch-through: 12

pgsql: doc: FreeBSD uses camcontrol identify, not atacontrol, for cache

doc: FreeBSD uses camcontrol identify, not atacontrol, for cache This is for IDE drive cache control, same as SCSI (already documented properly). Reported-by: John Ekins Discussion: https://postgr.es/m/20170808224017.8424.69...@wrigleys.postgresql.org Author: John Ekins Backpatch-through: 12

pgsql: doc: FreeBSD uses camcontrol identify, not atacontrol, for cache

doc: FreeBSD uses camcontrol identify, not atacontrol, for cache This is for IDE drive cache control, same as SCSI (already documented properly). Reported-by: John Ekins Discussion: https://postgr.es/m/20170808224017.8424.69...@wrigleys.postgresql.org Author: John Ekins Backpatch-through: 12

pgsql: doc: FreeBSD uses camcontrol identify, not atacontrol, for cache

doc: FreeBSD uses camcontrol identify, not atacontrol, for cache This is for IDE drive cache control, same as SCSI (already documented properly). Reported-by: John Ekins Discussion: https://postgr.es/m/20170808224017.8424.69...@wrigleys.postgresql.org Author: John Ekins Backpatch-through: 12

pgsql: doc: FreeBSD uses camcontrol identify, not atacontrol, for cache

doc: FreeBSD uses camcontrol identify, not atacontrol, for cache This is for IDE drive cache control, same as SCSI (already documented properly). Reported-by: John Ekins Discussion: https://postgr.es/m/20170808224017.8424.69...@wrigleys.postgresql.org Author: John Ekins Backpatch-through: 12

pgsql: doc: vacuum_cost_limit controls when vacuum_cost_delay happens

doc: vacuum_cost_limit controls when vacuum_cost_delay happens Mention this relationship. Reported-by: Martín Marqués Discussion: https://postgr.es/m/cabeg9ltsavp4waknguyo-haiiowcb8xejqvddfhx_nfi5sj...@mail.gmail.com Author: Martín Marqués Backpatch-through: master Branch -- master

pgsql: doc: update query section to show LIMIT/OFFSET like SELECT

doc: update query section to show LIMIT/OFFSET like SELECT The parameter names were slightly better in SELECT, so make them match. Reported-by: Euler Taveira Discussion: https://postgr.es/m/cahe3wgh-eyuablg1vs3qthii1tgws31h-fyegrdda7otous...@mail.gmail.com Backpatch-through: master Branch

pgsql: doc: clarify handling of ts_headline() operators & extra words

doc: clarify handling of ts_headline() operators & extra words Reported-by: Ngigi Waithaka & Alex Malek Bug: 15172 Discussion: https://postgr.es/m/152461454026.19805.6310947081647212...@wrigleys.postgresql.org Backpatch-through: 16 Branch -- REL_16_STABLE Details ---

pgsql: doc: clarify handling of ts_headline() operators & extra words

doc: clarify handling of ts_headline() operators & extra words Reported-by: Ngigi Waithaka & Alex Malek Bug: 15172 Discussion: https://postgr.es/m/152461454026.19805.6310947081647212...@wrigleys.postgresql.org Backpatch-through: 16 Branch -- master Details ---

pgsql: psql: improve description consistency of \dTS data types

psql: improve description consistency of \dTS data types This was done particularly for geometric data types. Reported-by: Christoph Berg Discussion: https://postgr.es/m/ygi8leuk0wvmn...@msg.df7cb.de Co-authored-by: Kyotaro Horiguchi Backpatch-through: master Branch -- master Details

pgsql: doc: clarify handling of range upper/lower/upper_inf/lower_inf()

doc: clarify handling of range upper/lower/upper_inf/lower_inf() Clarify handling of infinite range bounds. Reported-by: jani.rahk...@iki.fi Discussion: https://postgr.es/m/160508672127.25505.8356390205508789...@wrigleys.postgresql.org Co-authored-by: Laurenz Albe Backpatch-through: 16

pgsql: doc: clarify handling of range upper/lower/upper_inf/lower_inf()

doc: clarify handling of range upper/lower/upper_inf/lower_inf() Clarify handling of infinite range bounds. Reported-by: jani.rahk...@iki.fi Discussion: https://postgr.es/m/160508672127.25505.8356390205508789...@wrigleys.postgresql.org Co-authored-by: Laurenz Albe Backpatch-through: 16

pgsql: doc: move ROW IS NULL examples to a different chapter

doc: move ROW IS NULL examples to a different chapter Also add examples. Reported-by: Wolfgang Walther Discussion: https://postgr.es/m/21ff8e9c-627a-f949-fb00-a41b9ddcc...@technowledgy.de Backpatch-through: master Branch -- master Details ---

pgsql: doc: clarify that pg_global can _only_ be used for system tabs.

doc: clarify that pg_global can _only_ be used for system tabs. Reported-by: zhoushulin1...@gmail.com Discussion: https://postgr.es/m/160499688847.25495.8682880307938679...@wrigleys.postgresql.org Backpatch-through: master Branch -- master Details ---

pgsql: Adjust file_fdw regression tests for acc95f29ef FREEZE commit

Adjust file_fdw regression tests for acc95f29ef FREEZE commit Reported-by: Tom Lane Discussion: https://postgr.es/m/2161529.1699899...@sss.pgh.pa.us Backpatch-through: master Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/e61a82c949353d9684d037a9a404fbb26b651535

Re: pgsql: doc: restructure ALTER DEFAULT PRIVILEGES

On Mon, Nov 13, 2023 at 07:28:01PM +, Bruce Momjian wrote: > doc: restructure ALTER DEFAULT PRIVILEGES > > Clarify that default privileges are not inherited and reorder > paragraphs. This is a follow up to a recent ALTER DEFAULT PRIVILEGES > doc patch. > > Repo

pgsql: doc: restructure ALTER DEFAULT PRIVILEGES

doc: restructure ALTER DEFAULT PRIVILEGES Clarify that default privileges are not inherited and reorder paragraphs. This is a follow up to a recent ALTER DEFAULT PRIVILEGES doc patch. Reported-by: Sanjay Minni Diagnosed-by: AMpxBo=M35hcH1g4Vg=krj0-77fojcvdrdivf5ksoadog-l...@mail.gmail.com

pgsql: doc: restructure ALTER DEFAULT PRIVILEGES

doc: restructure ALTER DEFAULT PRIVILEGES Clarify that default privileges are not inherited and reorder paragraphs. This is a follow up to a recent ALTER DEFAULT PRIVILEGES doc patch. Reported-by: Sanjay Minni Diagnosed-by: AMpxBo=M35hcH1g4Vg=krj0-77fojcvdrdivf5ksoadog-l...@mail.gmail.com

pgsql: doc: correct description of libpq's PQsetnonblocking() mode

doc: correct description of libpq's PQsetnonblocking() mode Reported-by: Yugo NAGATA Discussion: https://postgr.es/m/20210713115949.702986955f8ccf23fa810...@sraoss.co.jp Backpatch-through: 12-16, master already done Branch -- REL_13_STABLE Details ---

pgsql: doc: correct description of libpq's PQsetnonblocking() mode

doc: correct description of libpq's PQsetnonblocking() mode Reported-by: Yugo NAGATA Discussion: https://postgr.es/m/20210713115949.702986955f8ccf23fa810...@sraoss.co.jp Backpatch-through: 12-16, master already done Branch -- REL_16_STABLE Details ---

pgsql: doc: correct description of libpq's PQsetnonblocking() mode

doc: correct description of libpq's PQsetnonblocking() mode Reported-by: Yugo NAGATA Discussion: https://postgr.es/m/20210713115949.702986955f8ccf23fa810...@sraoss.co.jp Backpatch-through: 12-16, master already done Branch -- REL_14_STABLE Details ---

pgsql: doc: correct description of libpq's PQsetnonblocking() mode

doc: correct description of libpq's PQsetnonblocking() mode Reported-by: Yugo NAGATA Discussion: https://postgr.es/m/20210713115949.702986955f8ccf23fa810...@sraoss.co.jp Backpatch-through: 12-16, master already done Branch -- REL_15_STABLE Details ---

pgsql: doc: correct description of libpq's PQsetnonblocking() mode

doc: correct description of libpq's PQsetnonblocking() mode Reported-by: Yugo NAGATA Discussion: https://postgr.es/m/20210713115949.702986955f8ccf23fa810...@sraoss.co.jp Backpatch-through: 12-16, master already done Branch -- REL_12_STABLE Details ---

pgsql: doc: correct description of libpq's PQsetnonblocking() mode

doc: correct description of libpq's PQsetnonblocking() mode Reported-by: Yugo NAGATA Discussion: https://postgr.es/m/20210713115949.702986955f8ccf23fa810...@sraoss.co.jp Backpatch-through: master Branch -- master Details ---

pgsql: Add error about the use of FREEZE in COPY TO

Add error about the use of FREEZE in COPY TO Also clarify some other error wording. Reported-by: Kyotaro Horiguchi Discussion: https://postgr.es/m/20220802.133046.1941977979333284049.horikyota@gmail.com Backpatch-through: master Branch -- master Details ---

pgsql: doc: remove RUNAS instructions for pg_upgrade on Windows

doc: remove RUNAS instructions for pg_upgrade on Windows None of our other tools have such a recommendation. Reported-by: David G. Johnston Discussion: https://postgr.es/m/CAKFQuwbpqP_DB8WhthnwbsUOT_qB=ak3ppbsyvenqfh...@mail.gmail.com Backpatch-through: master Branch -- master

pgsql: doc: fix wording describing the checkpoint_flush_after GUC

doc: fix wording describing the checkpoint_flush_after GUC Reported-by: Evan Macbeth Discussion: https://postgr.es/m/155208475619.1380.12815553062985622...@wrigleys.postgresql.org Backpatch-through: master Branch -- master Details ---

pgsql: doc: remove unnecessary comma in postgres-fdw

doc: remove unnecessary comma in postgres-fdw Backpatch-through: master Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/80e278e436a7ad5cb4724d8b8ef39e79e4c3f5e6 Modified Files -- doc/src/sgml/postgres-fdw.sgml | 2 +- 1 file changed, 1 insertion(+), 1

pgsql: doc:: simplify introductory text

doc:: simplify introductory text Reported-by: Joshua D. Drake Discussion: https://postgr.es/m/5ac2c96d-37a6-18aa-08c4-327a6fbff...@commandprompt.com Author: Joshua D. Drake Backpatch-through: master Branch -- master Details ---

pgsql: README: remove duplicate download link & mention related softw.

README: remove duplicate download link & mention related softw. Reported-by: Daniel Westermann Discussion: https://postgr.es/m/db6pr0902mb2184f7965c9ea9070acfca43d2...@db6pr0902mb2184.eurprd09.prod.outlook.com Backpatch-through: master Branch -- master Details ---

pgsql: doc: change "system" to "cluster" where appropriate

doc: change "system" to "cluster" where appropriate Reported-by: Jeff Davis Discussion: https://postgr.es/m/d040a1144e0127a49e335d1244a4de102a2a443b.ca...@j-davis.com Backpatch-through: master Branch -- master Details ---

pgsql: doc: mention that ANALYZE does block DDL

doc: mention that ANALYZE does block DDL Reported-by: Aramaki Zyake Discussion: https://postgr.es/m/156628723253.1296.7377373462603881976%40wrigleys.postgresql.org Author: Aramaki Zyake Backpatch-through: master Branch -- master Details ---

pgsql: doc: move HBA reload instructions above the syntax details

doc: move HBA reload instructions above the syntax details Reported-by: John Discussion: https://postgr.es/m/165947088723.651.7641196693246068...@wrigleys.postgresql.org Backpatch-through: master Branch -- master Details ---

pgsql: doc: \copy can get data values \. and end-of-input confused

doc: \copy can get data values \. and end-of-input confused Reported-by: Svante Richter Discussion: https://postgr.es/m/fcd57e4-8f23-4c3e-a5db-2571d0920...@beta.fastmail.com Backpatch-through: 11 Branch -- REL_11_STABLE Details ---

pgsql: doc: \copy can get data values \. and end-of-input confused

doc: \copy can get data values \. and end-of-input confused Reported-by: Svante Richter Discussion: https://postgr.es/m/fcd57e4-8f23-4c3e-a5db-2571d0920...@beta.fastmail.com Backpatch-through: 11 Branch -- REL_15_STABLE Details ---

pgsql: doc: \copy can get data values \. and end-of-input confused

doc: \copy can get data values \. and end-of-input confused Reported-by: Svante Richter Discussion: https://postgr.es/m/fcd57e4-8f23-4c3e-a5db-2571d0920...@beta.fastmail.com Backpatch-through: 11 Branch -- REL_16_STABLE Details ---

pgsql: doc: \copy can get data values \. and end-of-input confused

doc: \copy can get data values \. and end-of-input confused Reported-by: Svante Richter Discussion: https://postgr.es/m/fcd57e4-8f23-4c3e-a5db-2571d0920...@beta.fastmail.com Backpatch-through: 11 Branch -- REL_12_STABLE Details ---

pgsql: doc: \copy can get data values \. and end-of-input confused

doc: \copy can get data values \. and end-of-input confused Reported-by: Svante Richter Discussion: https://postgr.es/m/fcd57e4-8f23-4c3e-a5db-2571d0920...@beta.fastmail.com Backpatch-through: 11 Branch -- REL_13_STABLE Details ---

pgsql: doc: \copy can get data values \. and end-of-input confused

doc: \copy can get data values \. and end-of-input confused Reported-by: Svante Richter Discussion: https://postgr.es/m/fcd57e4-8f23-4c3e-a5db-2571d0920...@beta.fastmail.com Backpatch-through: 11 Branch -- master Details ---

pgsql: doc: \copy can get data values \. and end-of-input confused

doc: \copy can get data values \. and end-of-input confused Reported-by: Svante Richter Discussion: https://postgr.es/m/fcd57e4-8f23-4c3e-a5db-2571d0920...@beta.fastmail.com Backpatch-through: 11 Branch -- REL_14_STABLE Details ---

pgsql: doc: CREATE DATABASE doesn't copy db-level perms. from template

doc: CREATE DATABASE doesn't copy db-level perms. from template Reported-by: da...@kapitaltrading.com Discussion: https://postgr.es/m/166007719137.995877.13951579839074751...@wrigleys.postgresql.org Backpatch-through: 11 Branch -- REL_12_STABLE Details ---

pgsql: doc: CREATE DATABASE doesn't copy db-level perms. from template

doc: CREATE DATABASE doesn't copy db-level perms. from template Reported-by: da...@kapitaltrading.com Discussion: https://postgr.es/m/166007719137.995877.13951579839074751...@wrigleys.postgresql.org Backpatch-through: 11 Branch -- REL_16_STABLE Details ---

pgsql: doc: CREATE DATABASE doesn't copy db-level perms. from template

doc: CREATE DATABASE doesn't copy db-level perms. from template Reported-by: da...@kapitaltrading.com Discussion: https://postgr.es/m/166007719137.995877.13951579839074751...@wrigleys.postgresql.org Backpatch-through: 11 Branch -- REL_11_STABLE Details ---

pgsql: doc: CREATE DATABASE doesn't copy db-level perms. from template

doc: CREATE DATABASE doesn't copy db-level perms. from template Reported-by: da...@kapitaltrading.com Discussion: https://postgr.es/m/166007719137.995877.13951579839074751...@wrigleys.postgresql.org Backpatch-through: 11 Branch -- REL_15_STABLE Details ---

pgsql: doc: CREATE DATABASE doesn't copy db-level perms. from template

doc: CREATE DATABASE doesn't copy db-level perms. from template Reported-by: da...@kapitaltrading.com Discussion: https://postgr.es/m/166007719137.995877.13951579839074751...@wrigleys.postgresql.org Backpatch-through: 11 Branch -- master Details ---

pgsql: doc: CREATE DATABASE doesn't copy db-level perms. from template

doc: CREATE DATABASE doesn't copy db-level perms. from template Reported-by: da...@kapitaltrading.com Discussion: https://postgr.es/m/166007719137.995877.13951579839074751...@wrigleys.postgresql.org Backpatch-through: 11 Branch -- REL_14_STABLE Details ---

pgsql: doc: CREATE DATABASE doesn't copy db-level perms. from template

doc: CREATE DATABASE doesn't copy db-level perms. from template Reported-by: da...@kapitaltrading.com Discussion: https://postgr.es/m/166007719137.995877.13951579839074751...@wrigleys.postgresql.org Backpatch-through: 11 Branch -- REL_13_STABLE Details ---

pgsql: doc: mention ORDER BY for some aggregates, add ORDER BY examples

doc: mention ORDER BY for some aggregates, add ORDER BY examples Discussion: https://postgr.es/m/CAKFQuwb+4SWnfrfQKB-UM1P1x97Xk+ybSar4xM32XGLd=fq...@mail.gmail.com Co-authored-by: David G. Johnston Backpatch-through: master Branch -- master Details ---

pgsql: doc: ALTER DEFAULT PRIVILEGES does not affect inherited roles

doc: ALTER DEFAULT PRIVILEGES does not affect inherited roles Reported-by: Jordi Gutiérrez Hermoso Discussion: https://postgr.es/m/72652d72e1816bfc3c05d40f9e0e0373d07823c8.ca...@octave.org Co-authored-by: Laurenz Albe Backpatch-through: 11 Branch -- REL_15_STABLE Details ---

pgsql: doc: ALTER DEFAULT PRIVILEGES does not affect inherited roles

doc: ALTER DEFAULT PRIVILEGES does not affect inherited roles Reported-by: Jordi Gutiérrez Hermoso Discussion: https://postgr.es/m/72652d72e1816bfc3c05d40f9e0e0373d07823c8.ca...@octave.org Co-authored-by: Laurenz Albe Backpatch-through: 11 Branch -- REL_14_STABLE Details ---

pgsql: doc: ALTER DEFAULT PRIVILEGES does not affect inherited roles

doc: ALTER DEFAULT PRIVILEGES does not affect inherited roles Reported-by: Jordi Gutiérrez Hermoso Discussion: https://postgr.es/m/72652d72e1816bfc3c05d40f9e0e0373d07823c8.ca...@octave.org Co-authored-by: Laurenz Albe Backpatch-through: 11 Branch -- REL_13_STABLE Details ---

pgsql: doc: ALTER DEFAULT PRIVILEGES does not affect inherited roles

doc: ALTER DEFAULT PRIVILEGES does not affect inherited roles Reported-by: Jordi Gutiérrez Hermoso Discussion: https://postgr.es/m/72652d72e1816bfc3c05d40f9e0e0373d07823c8.ca...@octave.org Co-authored-by: Laurenz Albe Backpatch-through: 11 Branch -- REL_12_STABLE Details ---

pgsql: doc: ALTER DEFAULT PRIVILEGES does not affect inherited roles

doc: ALTER DEFAULT PRIVILEGES does not affect inherited roles Reported-by: Jordi Gutiérrez Hermoso Discussion: https://postgr.es/m/72652d72e1816bfc3c05d40f9e0e0373d07823c8.ca...@octave.org Co-authored-by: Laurenz Albe Backpatch-through: 11 Branch -- master Details ---

pgsql: doc: ALTER DEFAULT PRIVILEGES does not affect inherited roles

doc: ALTER DEFAULT PRIVILEGES does not affect inherited roles Reported-by: Jordi Gutiérrez Hermoso Discussion: https://postgr.es/m/72652d72e1816bfc3c05d40f9e0e0373d07823c8.ca...@octave.org Co-authored-by: Laurenz Albe Backpatch-through: 11 Branch -- REL_16_STABLE Details ---

pgsql: doc: ALTER DEFAULT PRIVILEGES does not affect inherited roles

doc: ALTER DEFAULT PRIVILEGES does not affect inherited roles Reported-by: Jordi Gutiérrez Hermoso Discussion: https://postgr.es/m/72652d72e1816bfc3c05d40f9e0e0373d07823c8.ca...@octave.org Co-authored-by: Laurenz Albe Backpatch-through: 11 Branch -- REL_11_STABLE Details ---

  1   2   3   4   5   6   7   8   9   10   >