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 Details --- https://git.postgresql.org/pg/commitdiff/151ffcf6d8c1a527fa3abc27b1a13c0d43be494e Modified Files -- src/tools/msvc/Mkvcbuild.pm | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
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 copies of the parse tree, while d3d55ce571 introduced self-join removal replacing relid of removed relation only in one of the copies. The present commit fixes this bug by making recurse_set_operations() call estimate_num_groups() with the copy of the parse tree processed by self-join removal. In future, we may think about maintaining just one copy of the parse tree and/or keeping removed relids as aliases. Reported-by: Zuming Jiang Bug: #18170 Discussion: https://postgr.es/m/flat/18170-f1d17bf9a0d58b24%40postgresql.org Author: Richard Guo, Alexander Korotkov Reviewed-by: Andrei Lepikhov Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/ec63622c03ff7be36d32c08aaa7d853856451488 Modified Files -- src/backend/optimizer/prep/prepunion.c | 7 +-- src/test/regress/expected/join.out | 17 + src/test/regress/sql/join.sql | 7 +++ 3 files changed, 29 insertions(+), 2 deletions(-)
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 Backpatch: 16-, where the meson build was introduced Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/a237a07d5351d7bb0afc6e0c41410d52915e47c8 Modified Files -- doc/src/sgml/meson.build | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
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 Backpatch: 16-, where the meson build was introduced Branch -- REL_16_STABLE Details --- https://git.postgresql.org/pg/commitdiff/f646ac6725672896d424e0ac46b3ba77a4063264 Modified Files -- doc/src/sgml/meson.build | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
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. Those'll be removed later. Branch -- REL_16_STABLE Details --- https://git.postgresql.org/pg/commitdiff/1e774846b870a858f8eb88b3f512562009177f45 Modified Files -- doc/src/sgml/release-16.sgml | 1568 +- 1 file changed, 1562 insertions(+), 6 deletions(-)
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/d594e0daf79f9e55d5308074d1ef801e9da285ac Modified Files -- doc/src/sgml/client-auth.sgml | 101 +- 1 file changed, 51 insertions(+), 50 deletions(-)
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/930bc76bec1021c9ab8c8cb41cc08d598c2e26d8 Modified Files -- doc/src/sgml/ref/psql-ref.sgml | 4 src/bin/psql/copy.c| 1 + 2 files changed, 5 insertions(+)
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/a5bee67c36cc05507e919ed1e2711a9c51f38afb Modified Files -- doc/src/sgml/ref/psql-ref.sgml | 4 src/bin/psql/copy.c| 1 + 2 files changed, 5 insertions(+)
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/7f85099f4b3bf0142b19e87b5596a63c2df96274 Modified Files -- doc/src/sgml/ref/psql-ref.sgml | 4 src/bin/psql/copy.c| 1 + 2 files changed, 5 insertions(+)
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/36726b7882180b798768239060e462fc9c184d27 Modified Files -- doc/src/sgml/ref/psql-ref.sgml | 4 src/bin/psql/copy.c| 1 + 2 files changed, 5 insertions(+)
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/7186596db64a038150f03a02f3fcf9edb9f149c5 Modified Files -- doc/src/sgml/ref/psql-ref.sgml | 4 src/bin/psql/copy.c| 1 + 2 files changed, 5 insertions(+)
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/42d3125adae176cb7dcf7a4d896a78e615f6bbb4 Modified Files -- doc/src/sgml/ref/psql-ref.sgml | 4 src/bin/psql/copy.c| 2 ++ 2 files changed, 6 insertions(+)
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/d1d80ef0115d5c7a079136403528a485c3c48586 Modified Files -- doc/src/sgml/ref/psql-ref.sgml | 4 src/bin/psql/copy.c| 1 + 2 files changed, 5 insertions(+)
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/pg/commitdiff/019317756673a5e55171918ab6a2a9a1ebf48648 Modified Files -- doc/src/sgml/manage-ag.sgml | 6 ++ 1 file changed, 6 insertions(+)
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/pg/commitdiff/d5b1045e672c5a0c1abf6033916f08caaf6f Modified Files -- doc/src/sgml/manage-ag.sgml | 6 ++ 1 file changed, 6 insertions(+)
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/pg/commitdiff/54af107cb119fb635c912362a425242bccffb485 Modified Files -- doc/src/sgml/manage-ag.sgml | 6 ++ 1 file changed, 6 insertions(+)
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/pg/commitdiff/31a89ddeb8ebe1904a4a2fc8914f577c6ceb9dee Modified Files -- doc/src/sgml/manage-ag.sgml | 6 ++ 1 file changed, 6 insertions(+)
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/commitdiff/d391f6dcc377b961628510ee7049d78032816ac0 Modified Files -- doc/src/sgml/manage-ag.sgml | 6 ++ 1 file changed, 6 insertions(+)
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/pg/commitdiff/e29f8e7535f4bb68e30de8066e6aba460d0f072c Modified Files -- doc/src/sgml/manage-ag.sgml | 6 ++ 1 file changed, 6 insertions(+)
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/pg/commitdiff/bf7584e4c7f759e7584b82f9353f61ba4a9d3f21 Modified Files -- doc/src/sgml/manage-ag.sgml | 6 ++ 1 file changed, 6 insertions(+)
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/commitdiff/77513529420253626e41df967d54e76510782c64 Modified Files -- doc/src/sgml/func.sgml | 26 ++ doc/src/sgml/syntax.sgml | 38 +- 2 files changed, 43 insertions(+), 21 deletions(-)
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 -- src/bin/pg_upgrade/check.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
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 -- src/bin/pg_upgrade/check.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
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 -- src/bin/pg_upgrade/check.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
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 -- src/bin/pg_upgrade/check.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
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). However, it didn't get really bad until b23cd185f removed the convert-a-table-to-a-view logic, which had made it possible for scripts that thought they were attaching ON SELECTs to tables to still work. Rewrite into a form that makes it clear that an ON SELECT rule is better regarded as an implementation detail of a view. Pre-v16, point out that adding ON SELECT to a table actually converts it to a view. Per bug #18178 from Joshua Uyehara. Back-patch to all supported branches. Discussion: https://postgr.es/m/18178-05534d7064044...@postgresql.org Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/95a610b0970d887a4733633a14f29a537129f160 Modified Files -- doc/src/sgml/ref/create_rule.sgml | 19 ++- 1 file changed, 10 insertions(+), 9 deletions(-)
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). However, it didn't get really bad until b23cd185f removed the convert-a-table-to-a-view logic, which had made it possible for scripts that thought they were attaching ON SELECTs to tables to still work. Rewrite into a form that makes it clear that an ON SELECT rule is better regarded as an implementation detail of a view. Pre-v16, point out that adding ON SELECT to a table actually converts it to a view. Per bug #18178 from Joshua Uyehara. Back-patch to all supported branches. Discussion: https://postgr.es/m/18178-05534d7064044...@postgresql.org Branch -- REL_13_STABLE Details --- https://git.postgresql.org/pg/commitdiff/111364ec20e1acc497b6925ab8d09fa753892c0b Modified Files -- doc/src/sgml/ref/create_rule.sgml | 20 +++- 1 file changed, 11 insertions(+), 9 deletions(-)
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). However, it didn't get really bad until b23cd185f removed the convert-a-table-to-a-view logic, which had made it possible for scripts that thought they were attaching ON SELECTs to tables to still work. Rewrite into a form that makes it clear that an ON SELECT rule is better regarded as an implementation detail of a view. Pre-v16, point out that adding ON SELECT to a table actually converts it to a view. Per bug #18178 from Joshua Uyehara. Back-patch to all supported branches. Discussion: https://postgr.es/m/18178-05534d7064044...@postgresql.org Branch -- REL_15_STABLE Details --- https://git.postgresql.org/pg/commitdiff/58d3283b675639a72faaef669371d71423be441b Modified Files -- doc/src/sgml/ref/create_rule.sgml | 20 +++- 1 file changed, 11 insertions(+), 9 deletions(-)
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). However, it didn't get really bad until b23cd185f removed the convert-a-table-to-a-view logic, which had made it possible for scripts that thought they were attaching ON SELECTs to tables to still work. Rewrite into a form that makes it clear that an ON SELECT rule is better regarded as an implementation detail of a view. Pre-v16, point out that adding ON SELECT to a table actually converts it to a view. Per bug #18178 from Joshua Uyehara. Back-patch to all supported branches. Discussion: https://postgr.es/m/18178-05534d7064044...@postgresql.org Branch -- REL_16_STABLE Details --- https://git.postgresql.org/pg/commitdiff/9d4ea0bb3fd461164b061f19885d565cfcf57f93 Modified Files -- doc/src/sgml/ref/create_rule.sgml | 19 ++- 1 file changed, 10 insertions(+), 9 deletions(-)
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). However, it didn't get really bad until b23cd185f removed the convert-a-table-to-a-view logic, which had made it possible for scripts that thought they were attaching ON SELECTs to tables to still work. Rewrite into a form that makes it clear that an ON SELECT rule is better regarded as an implementation detail of a view. Pre-v16, point out that adding ON SELECT to a table actually converts it to a view. Per bug #18178 from Joshua Uyehara. Back-patch to all supported branches. Discussion: https://postgr.es/m/18178-05534d7064044...@postgresql.org Branch -- REL_11_STABLE Details --- https://git.postgresql.org/pg/commitdiff/3f9fe9b76f908e7ebf697c6b96f39601b6f803f3 Modified Files -- doc/src/sgml/ref/create_rule.sgml | 20 +++- 1 file changed, 11 insertions(+), 9 deletions(-)
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). However, it didn't get really bad until b23cd185f removed the convert-a-table-to-a-view logic, which had made it possible for scripts that thought they were attaching ON SELECTs to tables to still work. Rewrite into a form that makes it clear that an ON SELECT rule is better regarded as an implementation detail of a view. Pre-v16, point out that adding ON SELECT to a table actually converts it to a view. Per bug #18178 from Joshua Uyehara. Back-patch to all supported branches. Discussion: https://postgr.es/m/18178-05534d7064044...@postgresql.org Branch -- REL_12_STABLE Details --- https://git.postgresql.org/pg/commitdiff/1f7d7f102d14082336c862a11dff1f4849437f7a Modified Files -- doc/src/sgml/ref/create_rule.sgml | 20 +++- 1 file changed, 11 insertions(+), 9 deletions(-)
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). However, it didn't get really bad until b23cd185f removed the convert-a-table-to-a-view logic, which had made it possible for scripts that thought they were attaching ON SELECTs to tables to still work. Rewrite into a form that makes it clear that an ON SELECT rule is better regarded as an implementation detail of a view. Pre-v16, point out that adding ON SELECT to a table actually converts it to a view. Per bug #18178 from Joshua Uyehara. Back-patch to all supported branches. Discussion: https://postgr.es/m/18178-05534d7064044...@postgresql.org Branch -- REL_14_STABLE Details --- https://git.postgresql.org/pg/commitdiff/f53f83b33e4203ec181c93b7fa5a2e9c70e73c31 Modified Files -- doc/src/sgml/ref/create_rule.sgml | 20 +++- 1 file changed, 11 insertions(+), 9 deletions(-)
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://git.postgresql.org/pg/commitdiff/1595724d00eb152296cfecae557a836963a67679 Modified Files -- doc/src/sgml/ref/alter_default_privileges.sgml | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-)
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://git.postgresql.org/pg/commitdiff/36c32af79e8034bf6da9c2d70ec427eb3b8a7556 Modified Files -- doc/src/sgml/ref/alter_default_privileges.sgml | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-)
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://git.postgresql.org/pg/commitdiff/f0a062d57a614a9cabc84f683e99789350ea1b46 Modified Files -- doc/src/sgml/ref/alter_default_privileges.sgml | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-)
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://git.postgresql.org/pg/commitdiff/421100b2edb4449fd3eb89f1672426382e8ffd4f Modified Files -- doc/src/sgml/ref/alter_default_privileges.sgml | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-)
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.postgresql.org/pg/commitdiff/a8510a7d96b9d0e7f1937801f9340bd02c539b7f Modified Files -- doc/src/sgml/ref/alter_default_privileges.sgml | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-)
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://git.postgresql.org/pg/commitdiff/8cb1d99f232da51c45ba46d7b14b659a24d6dfdc Modified Files -- doc/src/sgml/ref/alter_default_privileges.sgml | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-)
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://git.postgresql.org/pg/commitdiff/272db03bb9d5fbf55cfe39776973dae72cb4bec7 Modified Files -- doc/src/sgml/ref/alter_default_privileges.sgml | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-)
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 changed, 1 insertion(+)
