pgsql: Add missing unicode_category.c to MSVC build scripts

Add missing unicode_category.c to MSVC build scripts Fixes MSVC build failure introduced by a02b37fc0 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/39c959ef25bd9cdd966ee024ab14f8f4214bb276 Modified Files -- src/tools/msvc/Mkvcbuild.pm | 1 + 1 file cha

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 --- https:/

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 --- https:/

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 --- https://git.po

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 --- https:/

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 --- https:/

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 --- https:/

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 --- https:/

pgsql: Doc: update CREATE RULE ref page's hoary discussion of views.

Doc: update CREATE RULE ref page's hoary discussion of views. This text left one with the impression that an ON SELECT rule could be attached to a plain table, which has not been true since commit 264c06820 (meaning the text was already misleading when written, evidently by me in 96bd67f61). Howe

pgsql: Doc: update CREATE RULE ref page's hoary discussion of views.

Doc: update CREATE RULE ref page's hoary discussion of views. This text left one with the impression that an ON SELECT rule could be attached to a plain table, which has not been true since commit 264c06820 (meaning the text was already misleading when written, evidently by me in 96bd67f61). Howe

pgsql: Doc: update CREATE RULE ref page's hoary discussion of views.

Doc: update CREATE RULE ref page's hoary discussion of views. This text left one with the impression that an ON SELECT rule could be attached to a plain table, which has not been true since commit 264c06820 (meaning the text was already misleading when written, evidently by me in 96bd67f61). Howe

pgsql: Doc: update CREATE RULE ref page's hoary discussion of views.

Doc: update CREATE RULE ref page's hoary discussion of views. This text left one with the impression that an ON SELECT rule could be attached to a plain table, which has not been true since commit 264c06820 (meaning the text was already misleading when written, evidently by me in 96bd67f61). Howe

pgsql: Doc: update CREATE RULE ref page's hoary discussion of views.

Doc: update CREATE RULE ref page's hoary discussion of views. This text left one with the impression that an ON SELECT rule could be attached to a plain table, which has not been true since commit 264c06820 (meaning the text was already misleading when written, evidently by me in 96bd67f61). Howe

pgsql: Doc: update CREATE RULE ref page's hoary discussion of views.

Doc: update CREATE RULE ref page's hoary discussion of views. This text left one with the impression that an ON SELECT rule could be attached to a plain table, which has not been true since commit 264c06820 (meaning the text was already misleading when written, evidently by me in 96bd67f61). Howe

pgsql: Doc: update CREATE RULE ref page's hoary discussion of views.

Doc: update CREATE RULE ref page's hoary discussion of views. This text left one with the impression that an ON SELECT rule could be attached to a plain table, which has not been true since commit 264c06820 (meaning the text was already misleading when written, evidently by me in 96bd67f61). Howe

pgsql: pg_upgrade: Add missing newline to message

pg_upgrade: Add missing newline to message This was the backport of 2e3dc8c148, but in older releases the newline must be in the message. Branch -- REL_15_STABLE Details --- https://git.postgresql.org/pg/commitdiff/04d2d605f3a4d0d90f35e89c66a19c338ede0dd8 Modified Files -- s

pgsql: pg_upgrade: Add missing newline to message

pg_upgrade: Add missing newline to message This was the backport of 2e3dc8c148, but in older releases the newline must be in the message. Branch -- REL_12_STABLE Details --- https://git.postgresql.org/pg/commitdiff/d3246a2ad80359ad0740eb2cc5c849b3e09547d9 Modified Files -- s

pgsql: pg_upgrade: Add missing newline to message

pg_upgrade: Add missing newline to message This was the backport of 2e3dc8c148, but in older releases the newline must be in the message. Branch -- REL_13_STABLE Details --- https://git.postgresql.org/pg/commitdiff/2f1f49975f93edb59bebe2dcebecaa7e331e9d04 Modified Files -- s

pgsql: pg_upgrade: Add missing newline to message

pg_upgrade: Add missing newline to message This was the backport of 2e3dc8c148, but in older releases the newline must be in the message. Branch -- REL_14_STABLE Details --- https://git.postgresql.org/pg/commitdiff/f9280e77ecf4eaa17999f6c656b9008ced4cfa19 Modified Files -- s

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 --- https://git.postgresql.org/pg/co

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 --- https://git.postgresql.org/p

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 --- https://git.postgresql.org/p

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 --- https://git.postgresql.org/pg/commi

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 --- https://git.postgresql.org/p

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 --- https://git.postgresql.org/p

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 --- https://git.postgresql.org/p

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 --- https://git.postgresql.org/p

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 --- https://git.postgresql.org/pg/commitdiff/d1d80ef0115d

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 --- https://git.postgresql.org/pg/commitdiff/42d3125adae176cb7dc

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 --- https://git.postgresql.org/pg/commitdiff/7186596db64a

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 --- https://git.postgresql.org/pg/commitdiff/36726b788218

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 --- https://git.postgresql.org/pg/commitdiff/7f85099f4b3b

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 --- https://git.postgresql.org/pg/commitdiff/a5bee67c36cc

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 --- https://git.postgresql.org/pg/commitdiff/930bc76bec10

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 --- https://git.postgresql.org/pg/commitdiff/d594e0daf79f9e55d

pgsql: First-draft release notes for 16.1.

First-draft release notes for 16.1. As usual, the release notes for other branches will be made by cutting these down, but put them up for community review first. Also as usual for a .1 release, there are some entries here that are not really relevant for v16 because they already appeared in 16.0

pgsql: meson: docs: Install all manpages, not just ones in man1

meson: docs: Install all manpages, not just ones in man1 In f13eb16485f I made a mistake leading to only man1 being installed. I will report a bug suggesting that meson warn about mistakes of this sort. Reported-by: Christoph Berg Discussion: https://postgr.es/m/zuu5prqo6zueb...@msg.df7cb.de Bac

pgsql: meson: docs: Install all manpages, not just ones in man1

meson: docs: Install all manpages, not just ones in man1 In f13eb16485f I made a mistake leading to only man1 being installed. I will report a bug suggesting that meson warn about mistakes of this sort. Reported-by: Christoph Berg Discussion: https://postgr.es/m/zuu5prqo6zueb...@msg.df7cb.de Bac

pgsql: Fix usage of the parse tree for estimate_num_groups() in set ope

Fix usage of the parse tree for estimate_num_groups() in set operations recurse_set_operations() uses the parse tree for the group number estimation, because of the "varno 0" hack. At the same time 2489d76c49 made root->parse and corresponding parent_root->simple_rte_array[]->subquery distinct co

pgsql: Try again to fix the MSVC build

Try again to fix the MSVC build My last attempt in 39c959ef2 mistakenly conditionally added the missing file based on some unrelated condition. Reported-by: Thomas Munro Discussion: https://postgr.es/m/CA+hUKGLovvAXim9Fytn=jxks9s=JhP5=8oyy0cbxgg-ggal...@mail.gmail.com Branch -- master Deta