Reject MERGE in CTEs and COPY
The grammar added for MERGE inadvertently made it accepted syntax in
places that were not prepared to deal with it -- namely COPY and inside
CTEs, but invoking these things with MERGE currently causes assertion
failures or weird misbehavior in non-assertion builds. P
Reject MERGE in CTEs and COPY
The grammar added for MERGE inadvertently made it accepted syntax in
places that were not prepared to deal with it -- namely COPY and inside
CTEs, but invoking these things with MERGE currently causes assertion
failures or weird misbehavior in non-assertion builds. P
MERGE docs adjustments
Per Justin Pryzby
Discussion: https://postgr.es/m/20220801145257.ga15...@telsasoft.com
Discussion: https://postgr.es/m/20220714162618.gh18...@telsasoft.com
Branch
--
REL_15_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/d6d1fbf353d12b88509af40116ce900
MERGE docs adjustments
Per Justin Pryzby
Discussion: https://postgr.es/m/20220801145257.ga15...@telsasoft.com
Discussion: https://postgr.es/m/20220714162618.gh18...@telsasoft.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/3d895bc846f25859bd6dd242fbf204e6c5166e
Avoid using a fake relcache entry to own an SmgrRelation.
If an error occurs before we close the fake relcache entry, the the
fake relcache entry will be destroyed by the SmgrRelation will
survive until end of transaction. Its smgr_owner pointer ends up
pointing to already-freed memory.
The origi
Avoid using a fake relcache entry to own an SmgrRelation.
If an error occurs before we close the fake relcache entry, the the
fake relcache entry will be destroyed by the SmgrRelation will
survive until end of transaction. Its smgr_owner pointer ends up
pointing to already-freed memory.
The origi
doc: clarify DROP EXTENSION dependent members text
Member tracking was added in PG 13.
Reported-by: David G. Johnston
Discussion:
https://postgr.es/m/CAKFQuwY1YtxQHVWUFYvSnOjZ5VPpXjF33V52bSKEwFjK2K=1...@mail.gmail.com
Author: David G. Johnston
Backpatch-through: 13
Branch
--
REL_13_STAB
doc: clarify DROP EXTENSION dependent members text
Member tracking was added in PG 13.
Reported-by: David G. Johnston
Discussion:
https://postgr.es/m/CAKFQuwY1YtxQHVWUFYvSnOjZ5VPpXjF33V52bSKEwFjK2K=1...@mail.gmail.com
Author: David G. Johnston
Backpatch-through: 13
Branch
--
REL_14_STAB
doc: clarify DROP EXTENSION dependent members text
Member tracking was added in PG 13.
Reported-by: David G. Johnston
Discussion:
https://postgr.es/m/CAKFQuwY1YtxQHVWUFYvSnOjZ5VPpXjF33V52bSKEwFjK2K=1...@mail.gmail.com
Author: David G. Johnston
Backpatch-through: 13
Branch
--
master
Det
doc: clarify DROP EXTENSION dependent members text
Member tracking was added in PG 13.
Reported-by: David G. Johnston
Discussion:
https://postgr.es/m/CAKFQuwY1YtxQHVWUFYvSnOjZ5VPpXjF33V52bSKEwFjK2K=1...@mail.gmail.com
Author: David G. Johnston
Backpatch-through: 13
Branch
--
REL_15_STAB
doc: improve wal_level docs for the 'minimal' level
Reported-by: David G. Johnston
Discussion:
https://postgr.es/m/cakfquwz24ucfkoyllsw3pmgqatomocw1nuyfrumev-noof+...@mail.gmail.com
Author: David G. Johnston
Backpatch-through: 14, partial to 13
Branch
--
REL_15_STABLE
Details
---
ht
doc: improve wal_level docs for the 'minimal' level
Reported-by: David G. Johnston
Discussion:
https://postgr.es/m/cakfquwz24ucfkoyllsw3pmgqatomocw1nuyfrumev-noof+...@mail.gmail.com
Author: David G. Johnston
Backpatch-through: 14, partial to 13
Branch
--
REL_13_STABLE
Details
---
ht
doc: improve wal_level docs for the 'minimal' level
Reported-by: David G. Johnston
Discussion:
https://postgr.es/m/cakfquwz24ucfkoyllsw3pmgqatomocw1nuyfrumev-noof+...@mail.gmail.com
Author: David G. Johnston
Backpatch-through: 14, partial to 13
Branch
--
master
Details
---
https://g
doc: improve wal_level docs for the 'minimal' level
Reported-by: David G. Johnston
Discussion:
https://postgr.es/m/cakfquwz24ucfkoyllsw3pmgqatomocw1nuyfrumev-noof+...@mail.gmail.com
Author: David G. Johnston
Backpatch-through: 14, partial to 13
Branch
--
REL_14_STABLE
Details
---
ht
doc: clarify CREATE TABLE AS ... IF NOT EXISTS
Mention that the table is not modified if it already exists.
Reported-by: frank_limp...@yahoo.com
Discussion:
https://postgr.es/m/164441177106.9677.5991676148704507...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_15_STABLE
De
doc: clarify CREATE TABLE AS ... IF NOT EXISTS
Mention that the table is not modified if it already exists.
Reported-by: frank_limp...@yahoo.com
Discussion:
https://postgr.es/m/164441177106.9677.5991676148704507...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_13_STABLE
De
doc: clarify CREATE TABLE AS ... IF NOT EXISTS
Mention that the table is not modified if it already exists.
Reported-by: frank_limp...@yahoo.com
Discussion:
https://postgr.es/m/164441177106.9677.5991676148704507...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_10_STABLE
De
doc: clarify CREATE TABLE AS ... IF NOT EXISTS
Mention that the table is not modified if it already exists.
Reported-by: frank_limp...@yahoo.com
Discussion:
https://postgr.es/m/164441177106.9677.5991676148704507...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_14_STABLE
De
doc: clarify CREATE TABLE AS ... IF NOT EXISTS
Mention that the table is not modified if it already exists.
Reported-by: frank_limp...@yahoo.com
Discussion:
https://postgr.es/m/164441177106.9677.5991676148704507...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_12_STABLE
De
doc: clarify CREATE TABLE AS ... IF NOT EXISTS
Mention that the table is not modified if it already exists.
Reported-by: frank_limp...@yahoo.com
Discussion:
https://postgr.es/m/164441177106.9677.5991676148704507...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
master
Details
-
doc: clarify CREATE TABLE AS ... IF NOT EXISTS
Mention that the table is not modified if it already exists.
Reported-by: frank_limp...@yahoo.com
Discussion:
https://postgr.es/m/164441177106.9677.5991676148704507...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_11_STABLE
De
doc: document the CREATE INDEX "USING" clause
Somehow this was in the syntax but had no description.
Reported-by: robertcorring...@gmail.com
Discussion:
https://postgr.es/m/164228771825.31954.2719791849363756...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
master
Details
doc: document the CREATE INDEX "USING" clause
Somehow this was in the syntax but had no description.
Reported-by: robertcorring...@gmail.com
Discussion:
https://postgr.es/m/164228771825.31954.2719791849363756...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_11_STABLE
Detai
doc: document the CREATE INDEX "USING" clause
Somehow this was in the syntax but had no description.
Reported-by: robertcorring...@gmail.com
Discussion:
https://postgr.es/m/164228771825.31954.2719791849363756...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_13_STABLE
Detai
doc: document the CREATE INDEX "USING" clause
Somehow this was in the syntax but had no description.
Reported-by: robertcorring...@gmail.com
Discussion:
https://postgr.es/m/164228771825.31954.2719791849363756...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_15_STABLE
Detai
doc: document the CREATE INDEX "USING" clause
Somehow this was in the syntax but had no description.
Reported-by: robertcorring...@gmail.com
Discussion:
https://postgr.es/m/164228771825.31954.2719791849363756...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_10_STABLE
Detai
doc: document the CREATE INDEX "USING" clause
Somehow this was in the syntax but had no description.
Reported-by: robertcorring...@gmail.com
Discussion:
https://postgr.es/m/164228771825.31954.2719791849363756...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_12_STABLE
Detai
doc: document the CREATE INDEX "USING" clause
Somehow this was in the syntax but had no description.
Reported-by: robertcorring...@gmail.com
Discussion:
https://postgr.es/m/164228771825.31954.2719791849363756...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_14_STABLE
Detai
doc: clarify configuration file for Windows builds
The use of file 'config.pl' was not clearly explained.
Reported-by: liambo...@gmail.com
Discussion:
https://postgr.es/m/164246013804.31952.4958087335645367...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_14_STABLE
Details
doc: clarify configuration file for Windows builds
The use of file 'config.pl' was not clearly explained.
Reported-by: liambo...@gmail.com
Discussion:
https://postgr.es/m/164246013804.31952.4958087335645367...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_10_STABLE
Details
doc: clarify configuration file for Windows builds
The use of file 'config.pl' was not clearly explained.
Reported-by: liambo...@gmail.com
Discussion:
https://postgr.es/m/164246013804.31952.4958087335645367...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_12_STABLE
Details
doc: clarify configuration file for Windows builds
The use of file 'config.pl' was not clearly explained.
Reported-by: liambo...@gmail.com
Discussion:
https://postgr.es/m/164246013804.31952.4958087335645367...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_11_STABLE
Details
doc: clarify configuration file for Windows builds
The use of file 'config.pl' was not clearly explained.
Reported-by: liambo...@gmail.com
Discussion:
https://postgr.es/m/164246013804.31952.4958087335645367...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_15_STABLE
Details
doc: clarify configuration file for Windows builds
The use of file 'config.pl' was not clearly explained.
Reported-by: liambo...@gmail.com
Discussion:
https://postgr.es/m/164246013804.31952.4958087335645367...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
master
Details
--
doc: clarify configuration file for Windows builds
The use of file 'config.pl' was not clearly explained.
Reported-by: liambo...@gmail.com
Discussion:
https://postgr.es/m/164246013804.31952.4958087335645367...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_13_STABLE
Details
doc: warn about security issues around log files
Reported-by: Simon Riggs
Discussion:
https://postgr.es/m/canp8+jjesuuxyq9djvf-+tx2vy2oflmfeuu+uvwhnj1rt7i...@mail.gmail.com
Author: Simon Riggs
Backpatch-through: 10
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/co
doc: warn about security issues around log files
Reported-by: Simon Riggs
Discussion:
https://postgr.es/m/canp8+jjesuuxyq9djvf-+tx2vy2oflmfeuu+uvwhnj1rt7i...@mail.gmail.com
Author: Simon Riggs
Backpatch-through: 10
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdif
doc: warn about security issues around log files
Reported-by: Simon Riggs
Discussion:
https://postgr.es/m/canp8+jjesuuxyq9djvf-+tx2vy2oflmfeuu+uvwhnj1rt7i...@mail.gmail.com
Author: Simon Riggs
Backpatch-through: 10
Branch
--
REL_14_STABLE
Details
---
https://git.postgresql.org/pg/co
doc: warn about security issues around log files
Reported-by: Simon Riggs
Discussion:
https://postgr.es/m/canp8+jjesuuxyq9djvf-+tx2vy2oflmfeuu+uvwhnj1rt7i...@mail.gmail.com
Author: Simon Riggs
Backpatch-through: 10
Branch
--
REL_15_STABLE
Details
---
https://git.postgresql.org/pg/co
doc: warn about security issues around log files
Reported-by: Simon Riggs
Discussion:
https://postgr.es/m/canp8+jjesuuxyq9djvf-+tx2vy2oflmfeuu+uvwhnj1rt7i...@mail.gmail.com
Author: Simon Riggs
Backpatch-through: 10
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/co
doc: warn about security issues around log files
Reported-by: Simon Riggs
Discussion:
https://postgr.es/m/canp8+jjesuuxyq9djvf-+tx2vy2oflmfeuu+uvwhnj1rt7i...@mail.gmail.com
Author: Simon Riggs
Backpatch-through: 10
Branch
--
REL_11_STABLE
Details
---
https://git.postgresql.org/pg/co
doc: warn about security issues around log files
Reported-by: Simon Riggs
Discussion:
https://postgr.es/m/canp8+jjesuuxyq9djvf-+tx2vy2oflmfeuu+uvwhnj1rt7i...@mail.gmail.com
Author: Simon Riggs
Backpatch-through: 10
Branch
--
REL_12_STABLE
Details
---
https://git.postgresql.org/pg/co
doc: add section about heap-only tuples (HOT)
Reported-by: Jonathan S. Katz
Discussion:
https://postgr.es/m/c59ffbd5-96ac-a5a5-a401-14f627ca1...@postgresql.org
Backpatch-through: 11
Branch
--
REL_15_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/4445461cdff3580a2a698e89f
doc: add section about heap-only tuples (HOT)
Reported-by: Jonathan S. Katz
Discussion:
https://postgr.es/m/c59ffbd5-96ac-a5a5-a401-14f627ca1...@postgresql.org
Backpatch-through: 11
Branch
--
REL_11_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/99c1f24f5b5b0c1586e5dd143
doc: add section about heap-only tuples (HOT)
Reported-by: Jonathan S. Katz
Discussion:
https://postgr.es/m/c59ffbd5-96ac-a5a5-a401-14f627ca1...@postgresql.org
Backpatch-through: 11
Branch
--
REL_14_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/675a368a35a1ae4aa2c54fbd2
doc: add section about heap-only tuples (HOT)
Reported-by: Jonathan S. Katz
Discussion:
https://postgr.es/m/c59ffbd5-96ac-a5a5-a401-14f627ca1...@postgresql.org
Backpatch-through: 11
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/a9885f2c77e0ecbc9487a1c72
doc: add section about heap-only tuples (HOT)
Reported-by: Jonathan S. Katz
Discussion:
https://postgr.es/m/c59ffbd5-96ac-a5a5-a401-14f627ca1...@postgresql.org
Backpatch-through: 11
Branch
--
REL_12_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/f5078954f64e02d4c2317087b
doc: add section about heap-only tuples (HOT)
Reported-by: Jonathan S. Katz
Discussion:
https://postgr.es/m/c59ffbd5-96ac-a5a5-a401-14f627ca1...@postgresql.org
Backpatch-through: 11
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/115464bb5b4904e7536124eef168b7c1
doc: add missing role attributes to user management section
Reported-by: Shinya Kato
Discussion: https://postgr.es/m/1ecdb1ff78e9b03dfce37e85eaca7...@oss.nttdata.com
Author: Shinya Kato
Backpatch-through: 10
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff
doc: add missing role attributes to user management section
Reported-by: Shinya Kato
Discussion: https://postgr.es/m/1ecdb1ff78e9b03dfce37e85eaca7...@oss.nttdata.com
Author: Shinya Kato
Backpatch-through: 10
Branch
--
REL_14_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff
doc: add missing role attributes to user management section
Reported-by: Shinya Kato
Discussion: https://postgr.es/m/1ecdb1ff78e9b03dfce37e85eaca7...@oss.nttdata.com
Author: Shinya Kato
Backpatch-through: 10
Branch
--
REL_15_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff
doc: add missing role attributes to user management section
Reported-by: Shinya Kato
Discussion: https://postgr.es/m/1ecdb1ff78e9b03dfce37e85eaca7...@oss.nttdata.com
Author: Shinya Kato
Backpatch-through: 10
Branch
--
REL_11_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff
doc: add missing role attributes to user management section
Reported-by: Shinya Kato
Discussion: https://postgr.es/m/1ecdb1ff78e9b03dfce37e85eaca7...@oss.nttdata.com
Author: Shinya Kato
Backpatch-through: 10
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff
doc: add missing role attributes to user management section
Reported-by: Shinya Kato
Discussion: https://postgr.es/m/1ecdb1ff78e9b03dfce37e85eaca7...@oss.nttdata.com
Author: Shinya Kato
Backpatch-through: 10
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/fab54e
doc: add missing role attributes to user management section
Reported-by: Shinya Kato
Discussion: https://postgr.es/m/1ecdb1ff78e9b03dfce37e85eaca7...@oss.nttdata.com
Author: Shinya Kato
Backpatch-through: 10
Branch
--
REL_12_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff
pg_upgrade: Remove unused typedef
pgpid_t has been unused in pg_upgrade for a long time.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/c0408743c48fd9d6e34c40c38d8ca826e4a28525
Modified Files
--
src/bin/pg_upgrade/pg_upgrade.h | 3 ---
1 file changed, 3
pg_upgrade: Fix some minor code issues
96ef3b8ff1cf1950e897fd2f766d4bd9ef0d5d56 accidentally copied a not
applicable comment from the float8_pass_by_value code to the
data_checksums code. Remove that.
87d3b35a1ca31a9d947a8f919a6006679216dff0 changed pg_upgrade to
checking the checksum version ra
pg_upgrade: Fix some minor code issues
96ef3b8ff1cf1950e897fd2f766d4bd9ef0d5d56 accidentally copied a not
applicable comment from the float8_pass_by_value code to the
data_checksums code. Remove that.
87d3b35a1ca31a9d947a8f919a6006679216dff0 changed pg_upgrade to
checking the checksum version ra
pg_upgrade: Fix some minor code issues
96ef3b8ff1cf1950e897fd2f766d4bd9ef0d5d56 accidentally copied a not
applicable comment from the float8_pass_by_value code to the
data_checksums code. Remove that.
87d3b35a1ca31a9d947a8f919a6006679216dff0 changed pg_upgrade to
checking the checksum version ra
pg_upgrade: Fix some minor code issues
96ef3b8ff1cf1950e897fd2f766d4bd9ef0d5d56 accidentally copied a not
applicable comment from the float8_pass_by_value code to the
data_checksums code. Remove that.
87d3b35a1ca31a9d947a8f919a6006679216dff0 changed pg_upgrade to
checking the checksum version ra
pg_upgrade: Fix some minor code issues
96ef3b8ff1cf1950e897fd2f766d4bd9ef0d5d56 accidentally copied a not
applicable comment from the float8_pass_by_value code to the
data_checksums code. Remove that.
87d3b35a1ca31a9d947a8f919a6006679216dff0 changed pg_upgrade to
checking the checksum version ra
pg_upgrade: Fix some minor code issues
96ef3b8ff1cf1950e897fd2f766d4bd9ef0d5d56 accidentally copied a not
applicable comment from the float8_pass_by_value code to the
data_checksums code. Remove that.
87d3b35a1ca31a9d947a8f919a6006679216dff0 changed pg_upgrade to
checking the checksum version ra
pg_upgrade: Fix some minor code issues
96ef3b8ff1cf1950e897fd2f766d4bd9ef0d5d56 accidentally copied a not
applicable comment from the float8_pass_by_value code to the
data_checksums code. Remove that.
87d3b35a1ca31a9d947a8f919a6006679216dff0 changed pg_upgrade to
checking the checksum version ra
63 matches
Mail list logo