Re: Random pg_upgrade test failure on drongo
Alexander Law <exclusion@gmail.com>
From: Alexander Lakhin <exclusion@gmail.com>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>,
"pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>,
"andrew@dunslane.net" <andrew@dunslane.net>
Date: 2024-01-10T10:00:01Z
Lists: pgsql-hackers
10.01.2024 12:31, Amit Kapila wrote: > I am slightly hesitant to add any particular system table name in the > comments as this can happen for any other system table as well, so > slightly adjusted the comments in the attached. However, I think it is > okay to mention the particular system table name in the commit > message. Let me know what do you think. Thank you, Amit! I'd like to note that the culprit is exactly pg_largeobject as coded in dumpDatabase(): /* * pg_largeobject comes from the old system intact, so set its * relfrozenxids, relminmxids and relfilenode. */ if (dopt->binary_upgrade) ... appendPQExpBufferStr(loOutQry, "TRUNCATE pg_catalog.pg_largeobject;\n"); I see no other TRUNCATEs (or similar logic) around, so I would specify the table name in the comments. Though maybe I'm missing something... Best regards, Alexander
Commits
-
Fix an intermetant BF failure in 003_logical_slots.
- 6f97ef05d62a 17.0 landed