| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | New pg_config behavior |
| Date: | 2005-10-04 11:01:41 |
| Message-ID: | 200510041301.42404.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Schiltknecht | 2005-10-04 11:11:41 | memory bug debugging |
| Previous Message | Martijn van Oosterhout | 2005-10-04 10:37:47 | Re: Tuning current tuplesort external sort code for 8.2 |