Re: psql: immediately exit after an error?
От | Mike G |
---|---|
Тема | Re: psql: immediately exit after an error? |
Дата | |
Msg-id | 20040811042641.GD19602@localhost.localdomain обсуждение исходный текст |
Ответ на | psql: immediately exit after an error? (David Garamond <lists@zara.6.isreserved.com>) |
Список | pgsql-general |
I would think that depends upon how the sql in the file is coded. You can use the RAISE NOTICE / ERROR commands to aborta function's execution. > Can psql be told to exit immediately after an error (especially when > doing commands from a file, -f)? This is the default behaviour of the > mysql client, except when we give it -f option ("force"). > > The problem is, when restoring a dump, a failure at the some point might > cause the subsequent commands to produce wrong results (e.g. I redefine > a builtin function with a plruby function with different behaviour, but > plruby failed to be installed due to wrong path. Thus the subsequent > commands are executed using the builtin function which is not the > expected one.) Furthermore, you can't check on psql exit code to see > whether _any_ command was not successfully executed. > > Of course one should examine the full psql output after a restore > anyway, and the option to exit immediately after an error can save time > (especially for large dumps). > > -- > dave > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faqs/FAQ.html
В списке pgsql-general по дате отправления: