Re: Random pg_upgrade test failure on drongo
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
Cc: Alexander Lakhin <exclusion@gmail.com>, "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>, "andrew@dunslane.net" <andrew@dunslane.net>
Date: 2024-01-11T09:35:27Z
Lists: pgsql-hackers
On Thu, Jan 11, 2024 at 8:15 AM Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com> wrote: > > > > But tomorrow it could be for other tables and if we change this > > > TRUNCATE logic for pg_largeobject (of which chances are less) then > > > there is always a chance that one misses changing this comment. I feel > > > keeping it generic in this case would be better as the problem is > > > generic but it is currently shown for pg_largeobject. > > > > Yes, for sure. So let's keep it generic as you prefer. > > > > Thank you! > > Thanks for working the patch. I'm also OK to push the Amit's fix patch. > Thanks to both of you. I have pushed the patch. -- With Regards, Amit Kapila.
Commits
-
Fix an intermetant BF failure in 003_logical_slots.
- 6f97ef05d62a 17.0 landed