Re: adding a new column in IDENTIFY_SYSTEM

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jaime Casanova <jaime(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: adding a new column in IDENTIFY_SYSTEM
Date: 2011-05-04 02:47:34
Message-ID: 351.1304477254@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jaime Casanova <jaime(at)2ndquadrant(dot)com> writes:
> I want to propose the addition of a new field in IDENTIFY_SYSTEM:
> xlogversion, which will carry XLOG_PAGE_MAGIC from primary.
> The idea of sending that info is to allow us to know if the xlog page
> version of two different major versions are compatible or not.
> Currently pg_upgrade requires the primary to be taken down,

That's *intentional*.

The notion of WAL-shipping-replication compatibility between two
different major versions is insane on its face. They will not have
compatible system catalog contents. You might get perfect replication
of the master's catalogs, but the slave wouldn't be able to interpret
them.

The reason we have XLOG_PAGE_MAGIC is really more the opposite: to
prevent people from trying to recover across a minor version update in
which we had to break XLOG compatibility. I don't recall right now
if that's ever actually happened, but it definitely could.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2011-05-04 02:57:07 Re: Predicate locking
Previous Message Greg Smith 2011-05-04 02:36:13 Re: Predicate locking