Re: Random pg_upgrade test failure on drongo - Mailing list pgsql-hackers

From Alexander Lakhin
Subject Re: Random pg_upgrade test failure on drongo
Date
Msg-id 1a02bee2-77ae-5553-1417-5a7fd481cd42@gmail.com
Whole thread Raw
In response to Re: Random pg_upgrade test failure on drongo  (Amit Kapila <amit.kapila16@gmail.com>)
Responses RE: Random pg_upgrade test failure on drongo
List pgsql-hackers
10.01.2024 13:37, Amit Kapila 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!

Best regards,
Alexander



pgsql-hackers by date:

Previous
From: Anthonin Bonnefoy
Date:
Subject: Re: POC: Extension for adding distributed tracing - pg_tracing
Next
From: Jelte Fennema-Nio
Date:
Subject: Re: POC: Extension for adding distributed tracing - pg_tracing