Don't use the pg_am system catalog in new test

This causes deadlocks because it's a highly trafficked catalog.  Use a
regular table created by the same test instead.

Discussion: https://postgr.es/m/f3e61e27-19d0-5e40-3eb2-53282fa0532a@gmail.com
This commit is contained in:
Alvaro Herrera 2024-04-02 13:10:16 +02:00
parent 867cc7b6dd
commit 13b3b62746
No known key found for this signature in database
GPG Key ID: 1C20ACB9D5C564AE
2 changed files with 3 additions and 3 deletions

View File

@ -548,8 +548,8 @@ ERROR: access method "I do not exist AM" does not exist
CREATE TABLE i_am_a_failure() USING "btree";
ERROR: access method "btree" is not of type TABLE
-- Other weird invalid cases that cause problems
CREATE FOREIGN TABLE fp PARTITION OF pg_am DEFAULT SERVER x;
ERROR: "pg_am" is not partitioned
CREATE FOREIGN TABLE fp PARTITION OF tableam_parted_a_heap2 DEFAULT SERVER x;
ERROR: "tableam_parted_a_heap2" is not partitioned
-- Drop table access method, which fails as objects depends on it
DROP ACCESS METHOD heap2;
ERROR: cannot drop access method heap2 because other objects depend on it

View File

@ -349,7 +349,7 @@ CREATE TABLE i_am_a_failure() USING "I do not exist AM";
CREATE TABLE i_am_a_failure() USING "btree";
-- Other weird invalid cases that cause problems
CREATE FOREIGN TABLE fp PARTITION OF pg_am DEFAULT SERVER x;
CREATE FOREIGN TABLE fp PARTITION OF tableam_parted_a_heap2 DEFAULT SERVER x;
-- Drop table access method, which fails as objects depends on it
DROP ACCESS METHOD heap2;