Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: createdb argument question
- From: Gregory Stark <stark(at)enterprisedb(dot)com>
- To: "Perry Smith" <pedz(at)easesoftware(dot)com>
- Cc: "Seneca Cunningham" <tentra(at)gmail(dot)com>, <pgsql-general(at)postgresql(dot)org>
- Subject: Re: createdb argument question
- Date: Sun, 28 Oct 2007 20:11:46 +0000
"Perry Smith" <pedz(at)easesoftware(dot)com> writes: > The getopt_long on Mac and I guess also Linux have been made non- > Posix compliant. They accept options after the non-option argument. What is > really disturbing is they alter argv. I find that somewhat a bad idea but, I > guess no one really cares about consistency or traditions. You can get the traditional behaviour out of glibc if you set POSIXLY_CORRECT. One thing to beware of is that patch behaves very strangely with POSIXLY_CORRECT set though. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com
- References:
- createdb argument question
- From: Perry Smith
- Re: createdb argument question
- From: Seneca Cunningham
- Re: createdb argument question
- From: Perry Smith
- createdb argument question
- Prev by Date: Re: select count() out of memory
- Next by Date: Re: pg_restore
- Previous by thread: Re: createdb argument question
- Next by thread: Stored Procs Vs User Defined Functions vis-a-vis UDF's in Postgresql
- Indexes: