Re: alpha2 initdb PG_CONTROL_VERSION incompatibility?
От | Greg Smith |
---|---|
Тема | Re: alpha2 initdb PG_CONTROL_VERSION incompatibility? |
Дата | |
Msg-id | alpine.GSO.2.01.0911031511450.26156@westnet.com обсуждение исходный текст |
Ответ на | alpha2 initdb PG_CONTROL_VERSION incompatibility? (Lou Picciano <loupicciano@comcast.net>) |
Список | pgsql-testers |
On Tue, 3 Nov 2009, Lou Picciano wrote: > FATAL: database files are incompatible with server > DETAIL: The database cluster was initialized with PG_CONTROL_VERSION 843, but the server was compiled with > PG_CONTROL_VERSION 851 > > Strangely, these datafiles were init'd by 8.5 alpha1, and that server has been running without objection. > > However, we see the same log messages with 8.5 alpha2 against a freshly init'd cluster, built with alpha2's > initdb command, or when using data init'd by alpha1. Normally when this happens it's either because you're accidentially using the old initdb due to a PATH quirk you didn't anticipate, or PGDATA is pointing to the wrong place; maybe you set it explictly in initdb using "-d" but it's pointing at the wrong place? The troubleshooting path to figure out what causes this is to see if you're getting something that still points to the old version from the following: echo $PGDATA which initdb initdb --version which pg_ctl pg_ctl --version The other thing that can be helpful to confirm what is happening is to look at the output from pg_config to see where it put everything at. -- * Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD
В списке pgsql-testers по дате отправления: