| From: | Chuck McDevitt <cmcdevitt(at)greenplum(dot)com> |
|---|---|
| To: | "Zdenek(dot)Kotala(at)Sun(dot)COM" <Zdenek(dot)Kotala(at)Sun(dot)COM> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Solaris getopt_long and PostgreSQL |
| Date: | 2009-03-17 15:38:06 |
| Message-ID: | 2106D8DC89010842BABA5CD03FEA4061B249C901@EXVMBX018-10.exch018.msoutlookonline.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
About a year ago, you talked to the PostgreSQL people about some problem with Solaris getopt_long, and they changed the build to use the internal getopt_long instead of the Solaris one?
What was the problem with Solaris getopt_long? Does the problem still exist in Solaris 10?
My users are unhappy at the change, since normal getopt_long reorders the args, and apparently the built-in one doesn't, so "psql database -p port" no longer works, since it treats -p as the user name.
I don't know if I should revert that change, or port netBSD getopt_long and replace the PostgreSQL one with that.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-03-17 15:42:16 | Ignore -- testing message-id on footer |
| Previous Message | Dimitri Fontaine | 2009-03-17 15:21:37 | Re: small but useful patches for text search |