Re: xlogdump behaviour translating dropped relations - Mailing list pgsql-hackers

From Tom Lane
Subject Re: xlogdump behaviour translating dropped relations
Date
Msg-id 18298.1153948713@sss.pgh.pa.us
Whole thread Raw
In response to Re: xlogdump behaviour translating dropped relations  ("Diogo Biazus" <diogob@gmail.com>)
Responses Re: xlogdump behaviour translating dropped relations  ("Diogo Biazus" <diogob@gmail.com>)
List pgsql-hackers
"Diogo Biazus" <diogob@gmail.com> writes:
> On 7/26/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I'm not sure it should be making any attempt to translate anything.
>> What makes you think the oids even refer to the current database?

> I'm getting a new database connection based on the dbNode of the current
> xlog record. And I expect that the user informed a connection to the backend
> that originated the xlog files. Is this not going to work?

No.  I for one need this thing to analyze WAL dumps from databases
I don't even have access to, let alone have up-and-running locally.
It's really not going to be acceptable for the program to fail if it
can't have access to a database matching what it sees in the log.
The dropped-relation problem is just the first manifestation you happen
to have run into of why that's an unacceptable restriction, but there
are other reasons.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: [PATCHES] [PATCH] Provide 8-byte transaction IDs to
Next
From: Bruce Momjian
Date:
Subject: Re: [PATCHES] [PATCH] Provide 8-byte transaction IDs to