Re: Random pg_upgrade test failure on drongo
От | Amit Kapila |
---|---|
Тема | Re: Random pg_upgrade test failure on drongo |
Дата | |
Msg-id | CAA4eK1+RrK4VE_5z_W40gfcp7g8p799ma2u1+BS+VGo-XKEAdw@mail.gmail.com обсуждение исходный текст |
Ответ на | RE: Random pg_upgrade test failure on drongo ("Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>) |
Ответы |
RE: Random pg_upgrade test failure on drongo
|
Список | 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.
В списке pgsql-hackers по дате отправления: