Re: Did we really want to force an initdb in beta2?
От | Tom Lane |
---|---|
Тема | Re: Did we really want to force an initdb in beta2? |
Дата | |
Msg-id | 16262.1275665422@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Did we really want to force an initdb in beta2? (Dave Page <dpage@pgadmin.org>) |
Ответы |
Re: Did we really want to force an initdb in beta2?
Re: Did we really want to force an initdb in beta2? |
Список | pgsql-hackers |
Dave Page <dpage@pgadmin.org> writes: > On Fri, Jun 4, 2010 at 2:49 PM, Tom Lane <tgl@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
В списке pgsql-hackers по дате отправления: