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 26516.1545408037@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Check for conflicting queries during replay ofgistvacuumpage()  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: pgsql: Check for conflicting queries during replay of gistvacuumpage()  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: pgsql: Check for conflicting queries during replay of gistvacuumpage()  (Tom Lane <tgl@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 ofgistvacuumpage()  (Alvaro Herrera <alvherre@2ndquadrant.com>)
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?

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 by date:

Previous
From: Tom Lane
Date:
Subject: Re: Changes to pg_dump/psql following collation "C" in the catalog
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Check for conflicting queries during replay of gistvacuumpage()