Postgres Pro
Downloads
Home   >   mailing lists

Re: pgsql: Check for conflicting queries during replay of gistvacuumpage() - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pgsql: Check for conflicting queries during replay of gistvacuumpage()
Date
Msg-id 26932.1545408572@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Check for conflicting queries during replay of gistvacuumpage()  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql: Check for conflicting queries during replay of gistvacuumpage()  (Alexander Korotkov <a.korotkov@postgrespro.ru>)
Re: pgsql: Check for conflicting queries during replay of gistvacuumpage()  (Alexander Korotkov <a.korotkov@postgrespro.ru>)
List pgsql-hackers
Tree view 
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?

Oh, and if the answer to your question is not "it fails with an
intelligible error about an unrecognized WAL record type", then we
need to adjust what is emitted so that that will be what happens.
Crashing, or worse silently misprocessing the record, will not do.

            regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Check for conflicting queries during replay of gistvacuumpage()
Next
From: Alvaro Herrera
Date:
Subject: Re: pgsql: Check for conflicting queries during replay ofgistvacuumpage()