On Thu, 30 Jun 2005 09:11:13 -0400 Tom Lane <[EMAIL PROTECTED]> wrote:
> But congratulations on finding an entirely new way around the
> safety interlocks that are intended to prevent this sort of
> disaster. We shall have to think about whether we can fix that.
Glad to be of help, whatever way t
Ciprian Popovici <[EMAIL PROTECTED]> writes:
> Come to think of it better, at some point I might've switched
> repositories with 8.0 still running.
Hmm, you mean you renamed the 8.0 directory tree out of the way
and then moved the 7.4 tree where it had been, without stopping
the 8.0 postmaster? O
Oh, and FWIW, when I try a pg_dump on the database "recovered" with
pg_resetxlog, I get this:
pg_dump: missing pg_database entry for database "db"
--
Ciprian Popovici
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL
Quoting Tom Lane <[EMAIL PROTECTED]>:
> Ciprian Popovici <[EMAIL PROTECTED]> writes:
> > That is, a 8.0 which started on a 7.4.2 repository. After noticing,
> > I switched back to 7.4.2, but now it gives this error and won't start:
>
> I think you are omitting some relevant information, like what y
Ciprian Popovici <[EMAIL PROTECTED]> writes:
> That is, a 8.0 which started on a 7.4.2 repository. After noticing,
> I switched back to 7.4.2, but now it gives this error and won't start:
I think you are omitting some relevant information, like what you did
to force the 8.0 postmaster to start in
Hello,
I'm having the almost exact problem described here:
http://archives.postgresql.org/pgsql-admin/2004-12/msg00110.php
That is, a 8.0 which started on a 7.4.2 repository. After noticing,
I switched back to 7.4.2, but now it gives this error and won't start:
FATAL: database files are incompat
