Re: [BUGS] BUG #6034: pg_upgrade fails when it should not. - Mailing list pgsql-hackers

From Florian Pflug
Subject Re: [BUGS] BUG #6034: pg_upgrade fails when it should not.
Date
Msg-id 471C1E74-0A8F-45ED-8F31-3AFE10626A61@phlo.org
Whole thread Raw
In response to Re: [BUGS] BUG #6034: pg_upgrade fails when it should not.  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: [BUGS] BUG #6034: pg_upgrade fails when it should not.
List 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



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Bad UI design: pg_ctl and data_directory
Next
From: Radosław Smogura
Date:
Subject: BLOB support