| From: | Florian Pflug <fgp(at)phlo(dot)org> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 19:56:25 |
| Message-ID: | 471C1E74-0A8F-45ED-8F31-3AFE10626A61@phlo.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
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...
template1=# create database test lc_collate 'invalid' ;
ERROR: invalid locale name invalid
best regards,
Florian Pflug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-06-01 20:33:02 | Re: [BUGS] BUG #6034: pg_upgrade fails when it should not. |
| Previous Message | Cédric Villemain | 2011-06-01 18:43:46 | Re: Unlogged tables cannot be truncated twice |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Radosław Smogura | 2011-06-01 20:00:31 | BLOB support |
| Previous Message | Josh Berkus | 2011-06-01 19:55:56 | Bad UI design: pg_ctl and data_directory |