New pg_config behavior

Started by Peter Eisentrautover 20 years ago2 messages
#1Peter Eisentraut
peter_e@gmx.net

I have some doubts about the new pg_config behavior of printing "not recorded"
when an item is not known. I doubt that this will cause automated users of
this program to behave reasonably in error scenarios. I think a more
reasonable behavior would be to use a non-zero exit status and possibly print
a message to stderr and nothing to stdout.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Peter Eisentraut (#1)
Re: New pg_config behavior

Peter Eisentraut <peter_e@gmx.net> writes:

I have some doubts about the new pg_config behavior of printing "not recorded"
when an item is not known. I doubt that this will cause automated users of
this program to behave reasonably in error scenarios. I think a more
reasonable behavior would be to use a non-zero exit status and possibly print
a message to stderr and nothing to stdout.

Good point, although in practice that code only gets compiled in builds
with brain-dead Windows tools; I rather doubt that the resulting executable
would ever get used as you foresee. But if you want to change it, OK
with me.

regards, tom lane