pg.ddx.io pgsql-committers@postgresql.org mailing list archive
help / color / mirror / Atom feedpgsql: Avoid ERROR at ON COMMIT DELETE ROWS after relhassubclass=f.
6+ messages / 1 participants
[nested] [flat]
* pgsql: Avoid ERROR at ON COMMIT DELETE ROWS after relhassubclass=f.
@ 2025-04-20 15:30 Noah Misch <noah@leadboat.com>
0 siblings, 0 replies; 6+ messages in thread
From: Noah Misch @ 2025-04-20 15:30 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Avoid ERROR at ON COMMIT DELETE ROWS after relhassubclass=f.
Commit 7102070329d8147246d2791321f9915c3b5abf31 fixed a similar bug, but
it missed the case of database-wide ANALYZE ("use_own_xacts" mode).
Commit a07e03fd8fa7daf4d1356f7cb501ffe784ea6257 changed consequences
from silent discard of a pg_class stats (relpages et al.) update to
ERROR "tuple to be updated was already modified". Losing a relpages
update of an ON COMMIT DELETE ROWS table was negligible, but a
COMMIT-time error isn't negligible. Back-patch to v13 (all supported
versions).
Reported-by: Richard Guo <guofenglinux@gmail.com
Reported-by: Robins Tharakan <tharakan@gmail.com>
Discussion: https://postgr.es/m/CAMbWs4-XwMKMKJ_GT=p3_-_=j9rQSEs1FbDFUnW9zHuKPsPNEQ@mail.gmail.com
Backpatch-through: 13
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/2d5350cfbdc6e61124214d68713295bb060bc541
Modified Files
--------------
src/backend/commands/vacuum.c | 2 ++
src/test/regress/expected/maintain_every.out | 33 ++++++++++++++++++++++++++++
src/test/regress/parallel_schedule | 4 ++++
src/test/regress/sql/maintain_every.sql | 26 ++++++++++++++++++++++
4 files changed, 65 insertions(+)
^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Avoid ERROR at ON COMMIT DELETE ROWS after relhassubclass=f.
@ 2025-04-20 15:30 Noah Misch <noah@leadboat.com>
0 siblings, 0 replies; 6+ messages in thread
From: Noah Misch @ 2025-04-20 15:30 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Avoid ERROR at ON COMMIT DELETE ROWS after relhassubclass=f.
Commit 7102070329d8147246d2791321f9915c3b5abf31 fixed a similar bug, but
it missed the case of database-wide ANALYZE ("use_own_xacts" mode).
Commit a07e03fd8fa7daf4d1356f7cb501ffe784ea6257 changed consequences
from silent discard of a pg_class stats (relpages et al.) update to
ERROR "tuple to be updated was already modified". Losing a relpages
update of an ON COMMIT DELETE ROWS table was negligible, but a
COMMIT-time error isn't negligible. Back-patch to v13 (all supported
versions).
Reported-by: Richard Guo <guofenglinux@gmail.com
Reported-by: Robins Tharakan <tharakan@gmail.com>
Discussion: https://postgr.es/m/CAMbWs4-XwMKMKJ_GT=p3_-_=j9rQSEs1FbDFUnW9zHuKPsPNEQ@mail.gmail.com
Backpatch-through: 13
Branch
------
REL_13_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/d34b671a63e61d8e6002fb45f960d078e1073ea3
Modified Files
--------------
src/backend/commands/vacuum.c | 2 ++
src/test/regress/expected/maintain_every.out | 33 ++++++++++++++++++++++++++++
src/test/regress/parallel_schedule | 4 ++++
src/test/regress/sql/maintain_every.sql | 26 ++++++++++++++++++++++
4 files changed, 65 insertions(+)
^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Avoid ERROR at ON COMMIT DELETE ROWS after relhassubclass=f.
@ 2025-04-20 15:30 Noah Misch <noah@leadboat.com>
0 siblings, 0 replies; 6+ messages in thread
From: Noah Misch @ 2025-04-20 15:30 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Avoid ERROR at ON COMMIT DELETE ROWS after relhassubclass=f.
Commit 7102070329d8147246d2791321f9915c3b5abf31 fixed a similar bug, but
it missed the case of database-wide ANALYZE ("use_own_xacts" mode).
Commit a07e03fd8fa7daf4d1356f7cb501ffe784ea6257 changed consequences
from silent discard of a pg_class stats (relpages et al.) update to
ERROR "tuple to be updated was already modified". Losing a relpages
update of an ON COMMIT DELETE ROWS table was negligible, but a
COMMIT-time error isn't negligible. Back-patch to v13 (all supported
versions).
Reported-by: Richard Guo <guofenglinux@gmail.com
Reported-by: Robins Tharakan <tharakan@gmail.com>
Discussion: https://postgr.es/m/CAMbWs4-XwMKMKJ_GT=p3_-_=j9rQSEs1FbDFUnW9zHuKPsPNEQ@mail.gmail.com
Backpatch-through: 13
Branch
------
REL_17_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/d0a049987e5a0aab8bc79af889ff12349a325c97
Modified Files
--------------
src/backend/commands/vacuum.c | 2 ++
src/test/regress/expected/maintain_every.out | 33 ++++++++++++++++++++++++++++
src/test/regress/parallel_schedule | 4 ++++
src/test/regress/sql/maintain_every.sql | 26 ++++++++++++++++++++++
4 files changed, 65 insertions(+)
^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Avoid ERROR at ON COMMIT DELETE ROWS after relhassubclass=f.
@ 2025-04-20 15:30 Noah Misch <noah@leadboat.com>
0 siblings, 0 replies; 6+ messages in thread
From: Noah Misch @ 2025-04-20 15:30 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Avoid ERROR at ON COMMIT DELETE ROWS after relhassubclass=f.
Commit 7102070329d8147246d2791321f9915c3b5abf31 fixed a similar bug, but
it missed the case of database-wide ANALYZE ("use_own_xacts" mode).
Commit a07e03fd8fa7daf4d1356f7cb501ffe784ea6257 changed consequences
from silent discard of a pg_class stats (relpages et al.) update to
ERROR "tuple to be updated was already modified". Losing a relpages
update of an ON COMMIT DELETE ROWS table was negligible, but a
COMMIT-time error isn't negligible. Back-patch to v13 (all supported
versions).
Reported-by: Richard Guo <guofenglinux@gmail.com
Reported-by: Robins Tharakan <tharakan@gmail.com>
Discussion: https://postgr.es/m/CAMbWs4-XwMKMKJ_GT=p3_-_=j9rQSEs1FbDFUnW9zHuKPsPNEQ@mail.gmail.com
Backpatch-through: 13
Branch
------
REL_16_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/5905e993599917e9d978f31cdda6f540c3b3e4b2
Modified Files
--------------
src/backend/commands/vacuum.c | 2 ++
src/test/regress/expected/maintain_every.out | 33 ++++++++++++++++++++++++++++
src/test/regress/parallel_schedule | 4 ++++
src/test/regress/sql/maintain_every.sql | 26 ++++++++++++++++++++++
4 files changed, 65 insertions(+)
^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Avoid ERROR at ON COMMIT DELETE ROWS after relhassubclass=f.
@ 2025-04-20 15:30 Noah Misch <noah@leadboat.com>
0 siblings, 0 replies; 6+ messages in thread
From: Noah Misch @ 2025-04-20 15:30 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Avoid ERROR at ON COMMIT DELETE ROWS after relhassubclass=f.
Commit 7102070329d8147246d2791321f9915c3b5abf31 fixed a similar bug, but
it missed the case of database-wide ANALYZE ("use_own_xacts" mode).
Commit a07e03fd8fa7daf4d1356f7cb501ffe784ea6257 changed consequences
from silent discard of a pg_class stats (relpages et al.) update to
ERROR "tuple to be updated was already modified". Losing a relpages
update of an ON COMMIT DELETE ROWS table was negligible, but a
COMMIT-time error isn't negligible. Back-patch to v13 (all supported
versions).
Reported-by: Richard Guo <guofenglinux@gmail.com
Reported-by: Robins Tharakan <tharakan@gmail.com>
Discussion: https://postgr.es/m/CAMbWs4-XwMKMKJ_GT=p3_-_=j9rQSEs1FbDFUnW9zHuKPsPNEQ@mail.gmail.com
Backpatch-through: 13
Branch
------
REL_14_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/a61b67cd06c283d51cc833b4d1b990e6519836d8
Modified Files
--------------
src/backend/commands/vacuum.c | 2 ++
src/test/regress/expected/maintain_every.out | 33 ++++++++++++++++++++++++++++
src/test/regress/parallel_schedule | 4 ++++
src/test/regress/sql/maintain_every.sql | 26 ++++++++++++++++++++++
4 files changed, 65 insertions(+)
^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Avoid ERROR at ON COMMIT DELETE ROWS after relhassubclass=f.
@ 2025-04-20 15:30 Noah Misch <noah@leadboat.com>
0 siblings, 0 replies; 6+ messages in thread
From: Noah Misch @ 2025-04-20 15:30 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Avoid ERROR at ON COMMIT DELETE ROWS after relhassubclass=f.
Commit 7102070329d8147246d2791321f9915c3b5abf31 fixed a similar bug, but
it missed the case of database-wide ANALYZE ("use_own_xacts" mode).
Commit a07e03fd8fa7daf4d1356f7cb501ffe784ea6257 changed consequences
from silent discard of a pg_class stats (relpages et al.) update to
ERROR "tuple to be updated was already modified". Losing a relpages
update of an ON COMMIT DELETE ROWS table was negligible, but a
COMMIT-time error isn't negligible. Back-patch to v13 (all supported
versions).
Reported-by: Richard Guo <guofenglinux@gmail.com
Reported-by: Robins Tharakan <tharakan@gmail.com>
Discussion: https://postgr.es/m/CAMbWs4-XwMKMKJ_GT=p3_-_=j9rQSEs1FbDFUnW9zHuKPsPNEQ@mail.gmail.com
Backpatch-through: 13
Branch
------
REL_15_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/e0f53e6699697c24bbaccd8fd77e820e3e7f8248
Modified Files
--------------
src/backend/commands/vacuum.c | 2 ++
src/test/regress/expected/maintain_every.out | 33 ++++++++++++++++++++++++++++
src/test/regress/parallel_schedule | 4 ++++
src/test/regress/sql/maintain_every.sql | 26 ++++++++++++++++++++++
4 files changed, 65 insertions(+)
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2025-04-20 15:30 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-04-20 15:30 pgsql: Avoid ERROR at ON COMMIT DELETE ROWS after relhassubclass=f. Noah Misch <noah@leadboat.com>
2025-04-20 15:30 pgsql: Avoid ERROR at ON COMMIT DELETE ROWS after relhassubclass=f. Noah Misch <noah@leadboat.com>
2025-04-20 15:30 pgsql: Avoid ERROR at ON COMMIT DELETE ROWS after relhassubclass=f. Noah Misch <noah@leadboat.com>
2025-04-20 15:30 pgsql: Avoid ERROR at ON COMMIT DELETE ROWS after relhassubclass=f. Noah Misch <noah@leadboat.com>
2025-04-20 15:30 pgsql: Avoid ERROR at ON COMMIT DELETE ROWS after relhassubclass=f. Noah Misch <noah@leadboat.com>
2025-04-20 15:30 pgsql: Avoid ERROR at ON COMMIT DELETE ROWS after relhassubclass=f. Noah Misch <noah@leadboat.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox