> Not sure why would it matter that the pg_dump connection is read-only, this is about locking because > pg_dump needs to ensure the schema does not change while it's running. > pg_dump does not do > > LOCK TABLE gm.tableabc; > > but > > LOCK TABLE gm.tableabc IN ACCESS SHARE MODE; > > Which should be visible in pg_locks system view. And it does conflict with the ACCESS EXCLUSIVE mode, > used by the second query. My mistake. I cited the log incorrectly - of course should be (and there was) LOCK TABLE gm.tableabc IN ACCESS SHARE MODE. After all, your answer does not explain everything. I tried to reproduce the minimum commands: First session: BEGIN; set transaction isolation level repeatable read, read only; lock TABLE gm.tableabc IN access share mode; Second session: BEGIN; CREATE TEMP TABLE IF NOT EXISTS tableabc (Id BIGINT DEFAULT random()) INHERITS (gm.tableabc); "CREATE TEMP TABLE" does not wait for anything. Waiting state is only when I start third session with the same queries as in second. Maybe "LOCK TABLE ... IN ACCESS SHARE MODE" is the answer, but with correlation with some other query or setting setted by pg_backup. Table gm.tableabc is created with "create table gm.tableabc (x int default random());" AZ
