| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Florian Pflug <fgp(at)phlo(dot)org> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tim Uckun <timuckun(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [BUGS] BUG #6034: pg_upgrade fails when it should not. |
| Date: | 2011-06-01 20:33:02 |
| Message-ID: | 24405.1306960382@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Florian Pflug <fgp(at)phlo(dot)org> writes:
> On Jun1, 2011, at 20:28 , Peter Eisentraut wrote:
>> Well, initdb still succeeds if you give it an invalid locale name. It
>> warns, but that can easily be missed if initdb is hidden behind a few
>> other layers. If you then run pg_upgrade, you get a hosed instance.
> Whats the rational behind that behaviour? Wouldn't it be more user-friendly
> if initdb failed outright? It'd also be consistent with CREATE DATABASE...
I think we were being conservative about whether initdb would get it
right. Might be time to stiffen our spines a bit, now that the logic
has been through a few release cycles.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | wcting163 | 2011-06-02 02:53:01 | BUG #6047: prepare p1 as select 'now'::timestamp; then "execute p1" many times, they return the same time |
| Previous Message | Florian Pflug | 2011-06-01 19:56:25 | Re: [BUGS] BUG #6034: pg_upgrade fails when it should not. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cédric Villemain | 2011-06-01 20:34:38 | Re: [PERFORM] Hash Anti Join performance degradation |
| Previous Message | Robert Haas | 2011-06-01 20:31:34 | Re: [PERFORM] Hash Anti Join performance degradation |