pgsql: On Solaris, we should only force use of our own getopt(); it's - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: On Solaris, we should only force use of our own getopt(); it's
Date
Msg-id 20090327195811.C9698754ADE@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
On Solaris, we should only force use of our own getopt(); it's okay to use
the system's getopt_long().  The previous coding was the result of a sloppy
discussion that failed to draw this distinction.  The result was that PG
programs don't handle options as users of that platform expect.  Per
gripe from Chuck McDevitt.

Although this is a pre-existing bug, I'm not backpatching since I think we
could do with a bit of beta testing before concluding this is really OK.

Modified Files:
--------------
    pgsql:
        configure (r1.633 -> r1.634)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/configure?r1=1.633&r2=1.634)
        configure.in (r1.591 -> r1.592)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/configure.in?r1=1.591&r2=1.592)

pgsql-committers by date:

Previous
From: mha@postgresql.org (Magnus Hagander)
Date:
Subject: pgsql: Fix markup, per Devrim
Next
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Document in release notes that NOT IN is only for NOT EXIST