par_psql
par_psql copied to clipboard
Does not seem to respect --set ON_ERROR_STOP=1
I'm invoking par_psql with --set ON_ERROR_STOP=1
.
However, when one of my (parallelised) commands errored, par_psql continued on with the rest of the script.
I'll dig into it, but please let me know if you find a solution to this!
Hello Harry! Thanks for letting me know. I haven’t tested Par_psql with the last few major versions of Postgres. If I get time this week I’ll load it up and check what’s going on.
Graeme
On 16 Dec 2021, at 12:50, Harry Biddle @.***> wrote:
I'm invoking par_psql with --set ON_ERROR_STOP=1.
However, when one of my (parallelised) commands errored, par_psql continued on with the rest of the script.
I'll dig into it, but please let me know if you find a solution to this!
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.