| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(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-24 13:06:10 |
| Message-ID: | 20130124130610.GA19870@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 24, 2013 at 09:05:59AM +0530, Ashutosh Bapat wrote:
> I agree, answering the question, whether the particular attempt of
> starting a server succeeded or not, will need the current behaviour.
> Now, question is which of these behaviours should be default?
That would work. pg_upgrade knows the cluster version at that point and
can use the proper flag.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2013-01-24 13:07:29 | Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |
| Previous Message | Виктор Егоров | 2013-01-24 12:51:46 | Re: \d failing to find uppercased object names |