Re: Set new system identifier using pg_resetxlog - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Set new system identifier using pg_resetxlog
Date
Msg-id CA+Tgmob-JYj8k3TWeVR=fBhxD_fF-MuJ1ZRfFRyXa1SGc_Sk9Q@mail.gmail.com
Whole thread Raw
In response to Re: Set new system identifier using pg_resetxlog  (Heikki Linnakangas <hlinnakangas@vmware.com>)
List pgsql-hackers
On Mon, Aug 25, 2014 at 4:06 PM, Heikki Linnakangas
<hlinnakangas@vmware.com> wrote:
> I didn't understand this one. But it seems like the obvious solution is to
> not use the consumer's system identifier as the slot name. Or rename it
> afterwards.

You can't use the consumer's system identifier as the slot name,
because you have to create the slot before you create the consumer.
But you could rename it afterwards, or just use some other naming
convention entirely, which is why I'm -0.25 on this whole proposal.
What the 2ndQuadrant folks are proposing is not unreasonable (which is
why I'm only -0.25) but it opens an (admittedly small) can of worms
that I see no real need to open.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: postgresql latency & bgwriter not doing its job
Next
From: David G Johnston
Date:
Subject: Re: Code bug or doc bug?