Re: pg_upgrade should truncate/remove its logs before running
От | Tom Lane |
---|---|
Тема | Re: pg_upgrade should truncate/remove its logs before running |
Дата | |
Msg-id | 803503.1644194379@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: pg_upgrade should truncate/remove its logs before running (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: pg_upgrade should truncate/remove its logs before running
Re: pg_upgrade should truncate/remove its logs before running |
Список | pgsql-hackers |
Michael Paquier <michael@paquier.xyz> writes: > On Sun, Feb 06, 2022 at 08:32:59AM -0500, Andrew Dunstan wrote: >> But the commit really shouldn't have happened until we know that most >> buildfarm owners have installed it. It should have waited wait not just >> for the release but for widespread deployment. Otherwise we will just >> lose any logging for an error that might appear. > Would it be better if I just revert the change for now then and do it > again in one/two weeks? I don't see a need to revert it. I note, though, that there's still not been any email to the buildfarm owners list about this update. regards, tom lane
В списке pgsql-hackers по дате отправления: