Re: How to *really* quit psql?
От | Tom Lane |
---|---|
Тема | Re: How to *really* quit psql? |
Дата | |
Msg-id | 2628824.1668887377@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: How to *really* quit psql? (Greg Stark <stark@mit.edu>) |
Ответы |
Re: How to *really* quit psql?
|
Список | pgsql-hackers |
Greg Stark <stark@mit.edu> writes: > On Sat, 19 Nov 2022 at 14:10, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Under what circumstances would it be appropriate for a script to take >> it on itself to decide that? It has no way of knowing what the next -f >> option is or what the user intended. > Presumably when they're written by the same person so the script does > effectively know what the "user" intended because it's written by the > same user. Even so, embedding that knowledge in the first script doesn't seem like the sort of design we ought to encourage. It'd be better if "don't run the next script if the first one fails" were directed by a command-line switch or the like. I also wonder exactly how this interacts with existing features like ON_ERROR_STOP. regards, tom lane
В списке pgsql-hackers по дате отправления: