You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When \set ON_ERROR_STOP 'on' is present on user's own psqlrc or in the initialScript, if an error happens on the script, devenv seems to loose track of the original postgresql pid
ON_ERROR_STOP changes the behaviour of psql. By default, a scripting error still causes psql to complete successfully with error code 0. With ON_ERROR_STOP to "on", psql stops at the first error and returns 3.
It seems that this behaviour somehow makes devenv try to start another postgresql.
While this bug is about not loosing track of postgres's pid if psql fails for some reason, I'd also argue that ON_ERROR_STOP should actually be the default in the context of devenv.
Describe the bug
When
\set ON_ERROR_STOP 'on'
is present on user's own psqlrc or in theinitialScript
, if an error happens on the script, devenv seems to loose track of the original postgresql pidTo reproduce
Please use this gist: https://gist.github.com/autra/647f30ed267c99681f19522010b0bf30
The logs are like this:
Then, the last 5 lines are looping constantly.
If I type f9, process-compose exits, but the original postgres process still runs in the background.
Version
devenv 1.0.5 (x86_64-linux)
The text was updated successfully, but these errors were encountered: