From: Dave Page on
On Fri, Jun 4, 2010 at 4:30 PM, Tom Lane <tgl(a)sss.pgh.pa.us> wrote:
> Dave Page <dpage(a)pgadmin.org> writes:
>> On Fri, Jun 4, 2010 at 2:49 PM, Tom Lane <tgl(a)sss.pgh.pa.us> wrote:
>>> Right, because the catalog contents didn't change.  Seems to me you'd
>>> better teach the installers to look at PG_CONTROL_VERSION too.
>
>> Hmm, is there anything else that might need to be checked?
>
> Offhand I can think of three internal version-like numbers:
>
> CATALOG_VERSION_NO --- bump if initial system catalog contents would be
> inconsistent with backend code
>
> PG_CONTROL_VERSION --- bump when contents of pg_control change

They're easy enough.

> XLOG_PAGE_MAGIC --- bump on incompatible change in WAL contents

How can I get that from an existing data directory? I don't see it in
pg_controldata output (unless it has a non-obvious alias).


--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Tom Lane on
Dave Page <dpage(a)pgadmin.org> writes:
> On Fri, Jun 4, 2010 at 4:30 PM, Tom Lane <tgl(a)sss.pgh.pa.us> wrote:
>> XLOG_PAGE_MAGIC --- bump on incompatible change in WAL contents

> How can I get that from an existing data directory? I don't see it in
> pg_controldata output (unless it has a non-obvious alias).

You'd need to pull it out of one of the WAL files. I'm not sure it's
worth the trouble ...

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Dave Page on
On Fri, Jun 4, 2010 at 7:30 PM, Tom Lane <tgl(a)sss.pgh.pa.us> wrote:
> Dave Page <dpage(a)pgadmin.org> writes:
>> On Fri, Jun 4, 2010 at 4:30 PM, Tom Lane <tgl(a)sss.pgh.pa.us> wrote:
>>> XLOG_PAGE_MAGIC --- bump on incompatible change in WAL contents
>
>> How can I get that from an existing data directory? I don't see it in
>> pg_controldata output (unless it has a non-obvious alias).
>
> You'd need to pull it out of one of the WAL files.  I'm not sure it's
> worth the trouble ...

Urgh, no. Probably not.


--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers