| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Satoshi Nagayasu <snaga(at)uptime(dot)jp>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Michael Paquier <mpaquier(at)vmware(dot)com> |
| Subject: | Re: pg_rewind in contrib |
| Date: | 2015-01-14 21:57:49 |
| Message-ID: | CA+TgmobTDoGEyta2zx8bGcNLB8BhSfG29+LdruBsQDZSBvntJA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 7, 2015 at 8:44 AM, Andrew Dunstan <andrew(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-01-14 22:13:06 | Re: Out-of-bounds write and incorrect detection of trigger file in pg_standby |
| Previous Message | Tomas Vondra | 2015-01-14 21:52:58 | Re: PATCH: decreasing memory needlessly consumed by array_agg |