Re: pgsql: Check for conflicting queries during replay of gistvacuumpage()

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Alexander Korotkov <akorotkov(at)postgresql(dot)org>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Pg Committers <pgsql-committers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Check for conflicting queries during replay of gistvacuumpage()
Date: 2018-12-21 15:49:14
Message-ID: 20181221154914.bc7zjxwstf3ljqo4@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

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?

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2018-12-21 16:00:37 Re: pgsql: Check for conflicting queries during replay of gistvacuumpage()
Previous Message Alvaro Herrera 2018-12-21 14:05:37 Re: pgsql: Remove function names from error messages

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-12-21 15:57:22 Re: Changes to pg_dump/psql following collation "C" in the catalog
Previous Message Erik Rijkers 2018-12-21 15:25:38 Re: tickling the lesser contributor's withering ego