| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_ctl idempotent option |
| Date: | 2013-01-23 19:00:25 |
| Message-ID: | 51003349.2080109@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 23.01.2013 20:56, Bruce Momjian wrote:
> On Tue, Jan 22, 2013 at 06:03:28PM +0530, Ashutosh Bapat wrote:
>> anyway, +1 for making this as default option. Going that path, would
>> we be breaking backward compatibility? There might be scripts, (being
>> already used), which depend upon the current behaviour.
>
> FYI, I have a pg_upgrade patch that relies on the old throw-an-error
> behavior. Will there be a way to still throw an error if we make
> idempotent the default?
Could you check the status with "pg_ctl status" first, and throw an
error if it's not what you expected?
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2013-01-23 19:02:46 | COPY FREEZE has no warning |
| Previous Message | Bruce Momjian | 2013-01-23 18:58:24 | Re: [PATCH] pg_isready (was: [WIP] pg_ping utility) |