Re: pg_dump warning format?
| От | Erik Jones |
|---|---|
| Тема | Re: pg_dump warning format? |
| Дата | |
| Msg-id | 3F47464F-7CCC-4278-970C-5E10621F79EB@myemma.com обсуждение исходный текст |
| Ответ на | Re: pg_dump warning format? (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-general |
On Mar 15, 2007, at 9:08 PM, Tom Lane wrote:
Erik Jones <erik@myemma.com> writes:Basically I need a way for my script to know if it needs toabort because there were issues with the dump before it followsthrough with the drop db...Well, just checking the exit status from pg_dump ought to give you atleast a go/no-go indicator. If you want to be significantly moreparanoid, you could try the theory that *any* output to stderr isindicative of a problem.
Thanks. I guess I just wasn't sure as to whether or not anything other than "bad" messages were written to stderr. Given the intent of stderr you wouldn't think so, but I've seen cases where it was so.
erik jones <erik@myemma.com>
sofware developer
615-296-0838
emma(r)
В списке pgsql-general по дате отправления: