On August 25, 2014 9:45:50 PM CEST, Tom Lane <t...@sss.pgh.pa.us> wrote: >Heikki Linnakangas <hlinnakan...@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 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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
