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

From Andres Freund
Subject Re: Set new system identifier using pg_resetxlog
Date
Msg-id a01b5eca-5bd5-4386-985c-5b3f8b6abf02@email.android.com
Whole thread Raw
In response to Re: Set new system identifier using pg_resetxlog  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On August 25, 2014 9:45:50 PM CEST, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>Heikki Linnakangas <hlinnakangas@vmware.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
betweenall 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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Set new system identifier using pg_resetxlog
Next
From: Heikki Linnakangas
Date:
Subject: Re: psql \watch versus \timing