Thanks Tom. I had tried it with SU before I mailed the list and it didn't work. When I tried it again, I noticed that I typed a lower case C which it wouldn't accept. I tried it again with an upper case C and it worked. That's probably why my first attempt with SU failed and I didn't catch the error message before it rolled off the screen. The initdb on the initscript used to honor the extra switches. That's how I've been doing it since 8.2. I'll run it with SU from now on. Thanks! Scot Kreienkamp Senior Systems Engineer skreien@xxxxxxxxxxxx -----Original Message----- From: pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general-owner@xxxxxxxxxxxxxx] On Behalf Of Tom Lane Sent: Tuesday, December 13, 2011 12:00 AM To: Scot Kreienkamp Cc: Adrian Klaver; Postgres General (pgsql-general@xxxxxxxxxxxxxx) Subject: Re: initdb with lc-collate=C Scot Kreienkamp <SKreien@xxxxxxxxxxxx> writes: > There wasn't any output from the initdb other than OK. > [root@dvrv5030 9.1]# /etc/init.d/postgresql-9.1 initdb --lc-collate=C > Initializing database: [ OK ] Um. This isn't running initdb: this is running the package's initscript and hoping it will pass the switch you supplied through to initdb. If it doesn't, you'll get whatever locale is default in root's environment. I gather from the package name that you're using Devrim's packages not mine, so I don't know for sure what will happen here ... but I'm pretty sure that that extra switch would *not* be honored in the Red Hat/Fedora initscripts. My suggestion for this would be to "su - postgres" and then run initdb directly. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, please note that you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
