Re: Call for objections: deprecate postmaster -o switch?
| От | Tom Lane |
|---|---|
| Тема | Re: Call for objections: deprecate postmaster -o switch? |
| Дата | |
| Msg-id | 7399.1006739458@sss.pgh.pa.us обсуждение |
| Ответ на | Call for objections: deprecate postmaster -o switch? (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Call for objections: deprecate postmaster -o switch?
Re: Call for objections: deprecate postmaster -o switch? |
| Список | pgsql-hackers |
Bruce Momjian <pgman@candle.pha.pa.us> writes:
>> (a) did the sort_mem setting "take"?
> Sure did. I tried a sort value too low and it complained.
Okay, so the original bug is fixed on your version of BSD. (Which
is what, again?)
I looked a bit at configure and realized that we have no configure
test that causes src/utils/getopt.c to be selected. Apparently,
the *only* platform where src/utils/getopt.c is used is native WIN32,
so the "--foo" bug in it is irrelevant to the postmaster anyway.
But I'm still inclined to fix the bug.
It would be good to try to get a reading on whether there are any
current BSD distros that still have the getopt bug. But what I'm
inclined to do is note under the description of "--foo" that there
are a few older platforms where it won't work and you have to use -c,
rather than writing the docs on the assumption that -c is what most
people need to use.
regards, tom lane
В списке pgsql-hackers по дате отправления: