Re: Solaris getopt_long and PostgreSQL - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Solaris getopt_long and PostgreSQL
Date
Msg-id 20539.1237314382@sss.pgh.pa.us
Whole thread Raw
In response to Re: Solaris getopt_long and PostgreSQL  (Chuck McDevitt <cmcdevitt@greenplum.com>)
Responses Re: Solaris getopt_long and PostgreSQL  (Chuck McDevitt <cmcdevitt@greenplum.com>)
List pgsql-hackers
Chuck McDevitt <cmcdevitt@greenplum.com> writes:
> This is because MAC, BSD and GNU getopt_long permutes the arguments, and our getopt_long does not.

AFAIK those all work by scribbling on the original argv[] array, a
behavior that seems pretty risky from a portability standpoint.
Since our port/ module is only going to get used on old platforms with
no or broken getopt_long(), it needs to be pretty conservative about
what it assumes the system environment can handle.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Chuck McDevitt
Date:
Subject: Re: Solaris getopt_long and PostgreSQL
Next
From: Martijn van Oosterhout
Date:
Subject: Re: Problem with accesing Oracle from plperlu functionwhen using remote pg client.