Alvaro Herrera [EMAIL PROTECTED] writes:
Maybe the thing to do here is to disallow running a postmaster when the
data dir is using a different WAL magic (forcing you to pg_resetxlog or
initdb).
Which, curiously enough, is exactly what it does ...
I'm not particularly concerned with the
When starting up a postmaster from an older build on a database initialized
with a newer build I'm getting the following errors. I think I saw the same
thing earlier going in the opposite direction too. Shouldn't there be some
earlier errors firing from the control file version number?
[EMAIL
Gregory Stark wrote:
When starting up a postmaster from an older build on a database initialized
with a newer build I'm getting the following errors. I think I saw the same
thing earlier going in the opposite direction too. Shouldn't there be some
earlier errors firing from the control file
Alvaro Herrera [EMAIL PROTECTED] writes:
Gregory Stark wrote:
When starting up a postmaster from an older build on a database initialized
with a newer build I'm getting the following errors. I think I saw the same
thing earlier going in the opposite direction too. Shouldn't there be some
Gregory Stark wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Gregory Stark wrote:
When starting up a postmaster from an older build on a database initialized
with a newer build I'm getting the following errors. I think I saw the same
thing earlier going in the opposite direction
