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

From Diogo Biazus
Subject Re: xlogdump behaviour translating dropped relations
Date
Msg-id eca519a10607261343n543f4184j63dc7e872ee9b08@mail.gmail.com
Whole thread Raw
In response to Re: xlogdump behaviour translating dropped relations  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: xlogdump behaviour translating dropped relations  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

On 7/26/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"Diogo Biazus" <diogob@gmail.com> writes:
> I'm not sure about how the xlogdump should behave when translating oids of
> dropped relations.

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?

I know that we can have some problem with the db user (if he does not have access to all databases), but we can advise the user on the docs about it.


--
Diogo Biazus - diogob@gmail.com
Móvel Consultoria
http://www.movelinfo.com.br
http://www.postgresql.org.br

pgsql-hackers by date:

Previous
From: Darcy Buskermolen
Date:
Subject: Re: [PATCHES] [PATCH] Provide 8-byte transaction IDs to user level
Next
From: Tom Lane
Date:
Subject: Re: [PATCHES] extension for sql update