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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
