SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
04-11-2008, 06:05 AM
| ||||
| ||||
 New pg_config behavior 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/ ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster      |
|
04-11-2008, 06:05 AM
| ||||
| ||||
| 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 ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly |
Linear Mode
