From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Steve Singer <steve(at)ssinger(dot)info> |
Cc: | PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: 9.4 pg_control corruption |
Date: | 2014-07-09 02:14:31 |
Message-ID: | 9965.1404872071@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Steve Singer <steve(at)ssinger(dot)info> writes:
> I've encountered a corrupt pg_control file on my 9.4 development
> cluster. I've mostly been using the cluster for changeset extraction /
> slony testing.
> This is a 9.4 (currently commit 6ad903d70a440e + a walsender change
> discussed in another thread) but would have had the initdb done with an
> earlier 9.4 snapshot.
Somehow or other you missed the update to pg_control version number 942.
There's no obvious reason to think that this pg_control file is corrupt
on its own terms, but the pg_controldata version you're using expects
the 942 layout. The fact that the server wasn't complaining about this
suggests that you've not recompiled the server, or at least not xlog.c.
Possibly the odd failure to restart indicates that you have a partially
updated server executable?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Singer | 2014-07-09 02:36:41 | Re: 9.4 pg_control corruption |
Previous Message | Steve Singer | 2014-07-09 01:41:00 | 9.4 pg_control corruption |