From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Set new system identifier using pg_resetxlog |
Date: | 2014-08-25 19:52:24 |
Message-ID: | a01b5eca-5bd5-4386-985c-5b3f8b6abf02@email.android.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On August 25, 2014 9:45:50 PM CEST, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> writes:
>> In summary, I think we want this feature in some form, but we'll
>somehow
>> need to be make the distinction to the dangerous pg_resetxlog usage.
>It
>> might be best, after all, to make this a separate utility,
>> pg_resetsystemid.
>
>That sounds fairly reasonable given your point about not wanting people
>to
>confuse this with the can-eat-your-data aspects of pg_resetxlog.
>(OTOH,
>won't this result in a lot of code duplication? We'd still need to
>erase
>and refill the WAL area.)
Let's move pg-controldata, resetxlog, resetsysid into a common src/bin directory. Then we can unify the relevant code between all three.
--
Please excuse brevity and formatting - I am writing this on my mobile phone.
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2014-08-25 19:55:39 | Re: psql \watch versus \timing |
Previous Message | Heikki Linnakangas | 2014-08-25 19:48:40 | Re: psql \watch versus \timing |