Tom Lane wrote: > Florian Pflug <f...@phlo.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.
Do we want to revisit this? -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
