Re: visibility map corruption
От | Justin Pryzby |
---|---|
Тема | Re: visibility map corruption |
Дата | |
Msg-id | 20210708131114.GE22043@telsasoft.com обсуждение исходный текст |
Ответ на | Re: visibility map corruption ("Drouvot, Bertrand" <bdrouvot@amazon.com>) |
Ответы |
Re: visibility map corruption
|
Список | pgsql-hackers |
Also, the pg_upgrade status message still seems to be misplaced: In 20210706190612.GM22043@telsasoft.com, Justin Pryzby wrote: > I re-arranged the pg_upgrade output of that patch: it was in the middle of the > two halves: "Setting next transaction ID and epoch for new cluster" +++ b/src/bin/pg_upgrade/pg_upgrade.c @@ -473,6 +473,12 @@ copy_xact_xlog_xid(void) "\"%s/pg_resetwal\" -f -x %u \"%s\"", new_cluster.bindir, old_cluster.controldata.chkpnt_nxtxid, new_cluster.pgdata); + check_ok(); + prep_status("Setting oldest XID for new cluster"); + exec_prog(UTILITY_LOG_FILE, NULL, true, true, + "\"%s/pg_resetwal\" -f -u %u \"%s\"", + new_cluster.bindir, old_cluster.controldata.chkpnt_oldstxid, + new_cluster.pgdata); exec_prog(UTILITY_LOG_FILE, NULL, true, true, "\"%s/pg_resetwal\" -f -e %u \"%s\"", new_cluster.bindir, old_cluster.controldata.chkpnt_nxtepoch, -- Justin
В списке pgsql-hackers по дате отправления: