pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Fix temporary object cleanup failing due to toast access without 6+ messages / 1 participants [nested] [flat]
* pgsql: Fix temporary object cleanup failing due to toast access without @ 2022-02-21 18:35 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 6+ messages in thread From: Andres Freund @ 2022-02-21 18:35 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Fix temporary object cleanup failing due to toast access without snapshot. When cleaning up temporary objects during process exit the cleanup could fail with: FATAL: cannot fetch toast data without an active snapshot The bug is caused by RemoveTempRelationsCallback() not setting up a snapshot. If an object with toasted catalog data needs to be cleaned up, init_toast_snapshot() could fail with the above error. Most of the time however the the problem is masked due to cached catalog snapshots being returned by GetOldestSnapshot(). But dropping an object can cause catalog invalidations to be emitted. If no further catalog accesses are necessary between the invalidation processing and the next toast datum deletion, the bug becomes visible. It's easy to miss this bug because it typically happens after clients disconnect and the FATAL error just ends up in the log. Luckily temporary table cleanup at the next use of the same temporary schema or during DISCARD ALL does not have the same problem. Fix the bug by pushing a snapshot in RemoveTempRelationsCallback(). Also add isolation tests for temporary object cleanup, including objects with toasted catalog data. A future HEAD only commit will add more assertions. Reported-By: Miles Delahunty Author: Andres Freund Discussion: https://postgr.es/m/CAOFAq3BU5Mf2TTvu8D9n_ZOoFAeQswuzk7yziAb7xuw_qyw5gw@mail.gmail.com Backpatch: 10- Branch ------ REL_11_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/3faa21bb761f52974cfc59dd9d3993f89d81f44e Modified Files -------------- src/backend/catalog/namespace.c | 3 + .../isolation/expected/temp-schema-cleanup.out | 115 +++++++++++++++++++++ src/test/isolation/isolation_schedule | 1 + src/test/isolation/specs/temp-schema-cleanup.spec | 85 +++++++++++++++ 4 files changed, 204 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Fix temporary object cleanup failing due to toast access without @ 2022-02-21 18:35 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 6+ messages in thread From: Andres Freund @ 2022-02-21 18:35 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Fix temporary object cleanup failing due to toast access without snapshot. When cleaning up temporary objects during process exit the cleanup could fail with: FATAL: cannot fetch toast data without an active snapshot The bug is caused by RemoveTempRelationsCallback() not setting up a snapshot. If an object with toasted catalog data needs to be cleaned up, init_toast_snapshot() could fail with the above error. Most of the time however the the problem is masked due to cached catalog snapshots being returned by GetOldestSnapshot(). But dropping an object can cause catalog invalidations to be emitted. If no further catalog accesses are necessary between the invalidation processing and the next toast datum deletion, the bug becomes visible. It's easy to miss this bug because it typically happens after clients disconnect and the FATAL error just ends up in the log. Luckily temporary table cleanup at the next use of the same temporary schema or during DISCARD ALL does not have the same problem. Fix the bug by pushing a snapshot in RemoveTempRelationsCallback(). Also add isolation tests for temporary object cleanup, including objects with toasted catalog data. A future HEAD only commit will add more assertions. Reported-By: Miles Delahunty Author: Andres Freund Discussion: https://postgr.es/m/CAOFAq3BU5Mf2TTvu8D9n_ZOoFAeQswuzk7yziAb7xuw_qyw5gw@mail.gmail.com Backpatch: 10- Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/7bbfe5994165aef9e903b1919d625fe87d4f146e Modified Files -------------- src/backend/catalog/namespace.c | 3 + .../isolation/expected/temp-schema-cleanup.out | 116 +++++++++++++++++++++ src/test/isolation/isolation_schedule | 1 + src/test/isolation/specs/temp-schema-cleanup.spec | 85 +++++++++++++++ 4 files changed, 205 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Fix temporary object cleanup failing due to toast access without @ 2022-02-21 18:35 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 6+ messages in thread From: Andres Freund @ 2022-02-21 18:35 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Fix temporary object cleanup failing due to toast access without snapshot. When cleaning up temporary objects during process exit the cleanup could fail with: FATAL: cannot fetch toast data without an active snapshot The bug is caused by RemoveTempRelationsCallback() not setting up a snapshot. If an object with toasted catalog data needs to be cleaned up, init_toast_snapshot() could fail with the above error. Most of the time however the the problem is masked due to cached catalog snapshots being returned by GetOldestSnapshot(). But dropping an object can cause catalog invalidations to be emitted. If no further catalog accesses are necessary between the invalidation processing and the next toast datum deletion, the bug becomes visible. It's easy to miss this bug because it typically happens after clients disconnect and the FATAL error just ends up in the log. Luckily temporary table cleanup at the next use of the same temporary schema or during DISCARD ALL does not have the same problem. Fix the bug by pushing a snapshot in RemoveTempRelationsCallback(). Also add isolation tests for temporary object cleanup, including objects with toasted catalog data. A future HEAD only commit will add more assertions. Reported-By: Miles Delahunty Author: Andres Freund Discussion: https://postgr.es/m/CAOFAq3BU5Mf2TTvu8D9n_ZOoFAeQswuzk7yziAb7xuw_qyw5gw@mail.gmail.com Backpatch: 10- Branch ------ REL_12_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/0033fc63f5b2b763406f2299c426b9e1572fa244 Modified Files -------------- src/backend/catalog/namespace.c | 3 + .../isolation/expected/temp-schema-cleanup.out | 115 +++++++++++++++++++++ src/test/isolation/isolation_schedule | 1 + src/test/isolation/specs/temp-schema-cleanup.spec | 85 +++++++++++++++ 4 files changed, 204 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Fix temporary object cleanup failing due to toast access without @ 2022-02-21 18:35 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 6+ messages in thread From: Andres Freund @ 2022-02-21 18:35 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Fix temporary object cleanup failing due to toast access without snapshot. When cleaning up temporary objects during process exit the cleanup could fail with: FATAL: cannot fetch toast data without an active snapshot The bug is caused by RemoveTempRelationsCallback() not setting up a snapshot. If an object with toasted catalog data needs to be cleaned up, init_toast_snapshot() could fail with the above error. Most of the time however the the problem is masked due to cached catalog snapshots being returned by GetOldestSnapshot(). But dropping an object can cause catalog invalidations to be emitted. If no further catalog accesses are necessary between the invalidation processing and the next toast datum deletion, the bug becomes visible. It's easy to miss this bug because it typically happens after clients disconnect and the FATAL error just ends up in the log. Luckily temporary table cleanup at the next use of the same temporary schema or during DISCARD ALL does not have the same problem. Fix the bug by pushing a snapshot in RemoveTempRelationsCallback(). Also add isolation tests for temporary object cleanup, including objects with toasted catalog data. A future HEAD only commit will add more assertions. Reported-By: Miles Delahunty Author: Andres Freund Discussion: https://postgr.es/m/CAOFAq3BU5Mf2TTvu8D9n_ZOoFAeQswuzk7yziAb7xuw_qyw5gw@mail.gmail.com Backpatch: 10- Branch ------ REL_10_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/cebc54b90bda3ce43dc60faf216d2d149eebd3f3 Modified Files -------------- src/backend/catalog/namespace.c | 3 + .../isolation/expected/temp-schema-cleanup.out | 115 +++++++++++++++++++++ src/test/isolation/isolation_schedule | 1 + src/test/isolation/specs/temp-schema-cleanup.spec | 85 +++++++++++++++ 4 files changed, 204 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Fix temporary object cleanup failing due to toast access without @ 2022-02-21 18:35 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 6+ messages in thread From: Andres Freund @ 2022-02-21 18:35 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Fix temporary object cleanup failing due to toast access without snapshot. When cleaning up temporary objects during process exit the cleanup could fail with: FATAL: cannot fetch toast data without an active snapshot The bug is caused by RemoveTempRelationsCallback() not setting up a snapshot. If an object with toasted catalog data needs to be cleaned up, init_toast_snapshot() could fail with the above error. Most of the time however the the problem is masked due to cached catalog snapshots being returned by GetOldestSnapshot(). But dropping an object can cause catalog invalidations to be emitted. If no further catalog accesses are necessary between the invalidation processing and the next toast datum deletion, the bug becomes visible. It's easy to miss this bug because it typically happens after clients disconnect and the FATAL error just ends up in the log. Luckily temporary table cleanup at the next use of the same temporary schema or during DISCARD ALL does not have the same problem. Fix the bug by pushing a snapshot in RemoveTempRelationsCallback(). Also add isolation tests for temporary object cleanup, including objects with toasted catalog data. A future HEAD only commit will add more assertions. Reported-By: Miles Delahunty Author: Andres Freund Discussion: https://postgr.es/m/CAOFAq3BU5Mf2TTvu8D9n_ZOoFAeQswuzk7yziAb7xuw_qyw5gw@mail.gmail.com Backpatch: 10- Branch ------ REL_13_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/c2551483e0f6855183ae43a74abb3e434803b907 Modified Files -------------- src/backend/catalog/namespace.c | 3 + .../isolation/expected/temp-schema-cleanup.out | 115 +++++++++++++++++++++ src/test/isolation/isolation_schedule | 1 + src/test/isolation/specs/temp-schema-cleanup.spec | 85 +++++++++++++++ 4 files changed, 204 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Fix temporary object cleanup failing due to toast access without @ 2022-02-21 18:35 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 6+ messages in thread From: Andres Freund @ 2022-02-21 18:35 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Fix temporary object cleanup failing due to toast access without snapshot. When cleaning up temporary objects during process exit the cleanup could fail with: FATAL: cannot fetch toast data without an active snapshot The bug is caused by RemoveTempRelationsCallback() not setting up a snapshot. If an object with toasted catalog data needs to be cleaned up, init_toast_snapshot() could fail with the above error. Most of the time however the the problem is masked due to cached catalog snapshots being returned by GetOldestSnapshot(). But dropping an object can cause catalog invalidations to be emitted. If no further catalog accesses are necessary between the invalidation processing and the next toast datum deletion, the bug becomes visible. It's easy to miss this bug because it typically happens after clients disconnect and the FATAL error just ends up in the log. Luckily temporary table cleanup at the next use of the same temporary schema or during DISCARD ALL does not have the same problem. Fix the bug by pushing a snapshot in RemoveTempRelationsCallback(). Also add isolation tests for temporary object cleanup, including objects with toasted catalog data. A future HEAD only commit will add an assertion trying to make this more visible. Reported-By: Miles Delahunty Author: Andres Freund Discussion: https://postgr.es/m/CAOFAq3BU5Mf2TTvu8D9n_ZOoFAeQswuzk7yziAb7xuw_qyw5gw@mail.gmail.com Backpatch: 10- Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/7c38ef2a5d6cf6d8dc3834399d7a1c364d64ce64 Modified Files -------------- src/backend/catalog/namespace.c | 3 + .../isolation/expected/temp-schema-cleanup.out | 115 +++++++++++++++++++++ src/test/isolation/isolation_schedule | 1 + src/test/isolation/specs/temp-schema-cleanup.spec | 85 +++++++++++++++ 4 files changed, 204 insertions(+) ^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2022-02-21 18:35 UTC | newest] Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2022-02-21 18:35 pgsql: Fix temporary object cleanup failing due to toast access without Andres Freund <andres@anarazel.de> 2022-02-21 18:35 pgsql: Fix temporary object cleanup failing due to toast access without Andres Freund <andres@anarazel.de> 2022-02-21 18:35 pgsql: Fix temporary object cleanup failing due to toast access without Andres Freund <andres@anarazel.de> 2022-02-21 18:35 pgsql: Fix temporary object cleanup failing due to toast access without Andres Freund <andres@anarazel.de> 2022-02-21 18:35 pgsql: Fix temporary object cleanup failing due to toast access without Andres Freund <andres@anarazel.de> 2022-02-21 18:35 pgsql: Fix temporary object cleanup failing due to toast access without Andres Freund <andres@anarazel.de>
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