Dave Page <dp...@pgadmin.org> writes: > On Fri, Jun 4, 2010 at 2:49 PM, Tom Lane <t...@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 XLOG_PAGE_MAGIC --- bump on incompatible change in WAL contents regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers