Re: pg_rewind in contrib - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pg_rewind in contrib
Date
Msg-id CA+TgmobTDoGEyta2zx8bGcNLB8BhSfG29+LdruBsQDZSBvntJA@mail.gmail.com
Whole thread Raw
In response to Re: pg_rewind in contrib  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Wed, Jan 7, 2015 at 8:44 AM, Andrew Dunstan <andrew@dunslane.net> wrote:
> I understand, but I think "pg_rewind" is likely to be misleading to many
> users who will say "but I don't want just to rewind".
>
> I'm not wedded to the name I suggested, but I think we should look at
> possible alternative names. We do have experience of misleading names
> causing confusion (e.g. "initdb").

FWIW, pg_rewind sounds pretty good to me.  But maybe I'm just not
understanding what the use case for this, apart from rewinding?

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



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: PATCH: decreasing memory needlessly consumed by array_agg
Next
From: Robert Haas
Date:
Subject: Re: Out-of-bounds write and incorrect detection of trigger file in pg_standby