From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Dave Page <dpage(at)pgadmin(dot)org>, Florian Pflug <fgp(at)phlo(dot)org>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Did we really want to force an initdb in beta2? |
Date: | 2010-06-04 15:32:21 |
Message-ID: | 201006041532.o54FWL210180@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Dave Page <dpage(at)pgadmin(dot)org> writes:
> > On Fri, Jun 4, 2010 at 2:49 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
pg_upgrade never views these in their raw format so does not need to
check them. (It does look at pg_controldata text output.)
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ None of us is going to be here forever. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-06-04 15:45:12 | Re: Idea for getting rid of VACUUM FREEZE on cold pages |
Previous Message | Tom Lane | 2010-06-04 15:30:22 | Re: Did we really want to force an initdb in beta2? |