Re: pgsql: Check for conflicting queries during replay of gistvacuumpage()
От | Tom Lane |
---|---|
Тема | Re: pgsql: Check for conflicting queries during replay of gistvacuumpage() |
Дата | |
Msg-id | 26516.1545408037@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: pgsql: Check for conflicting queries during replay ofgistvacuumpage() (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Ответы |
Re: pgsql: Check for conflicting queries during replay of gistvacuumpage()
Re: pgsql: Check for conflicting queries during replay of gistvacuumpage() Re: pgsql: Check for conflicting queries during replay ofgistvacuumpage() Re: pgsql: Check for conflicting queries during replay ofgistvacuumpage() |
Список | pgsql-hackers |
Alvaro Herrera <alvherre@2ndquadrant.com> writes: > Hmmm, I'm fairly sure you should have bumped XLOG_PAGE_MAGIC for this > change. Otherwise, what is going to happen to an unpatched standby (of > released versions) that receives the new WAL record from a patched > primary? We can't change XLOG_PAGE_MAGIC in released branches, surely. I think the correct thing is just for the release notes to warn people to upgrade standby servers first. regards, tom lane
В списке pgsql-hackers по дате отправления: