diff options
author | Damien Baty <damien@damienbaty.com> | 2023-11-06 07:10:47 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-11-06 14:10:47 +0800 |
commit | 5050f01abce7aedd22e081588b4a057b207d31ce (patch) | |
tree | 8cc1fe356d488f83c792063d24b602e86457dd15 | |
parent | 04ca41a26259a83ebc027e8d16e4a63856ec6055 (diff) |
pgclirc: Clarify description of `destructive_warning_restarts_connection` option (#1437)
-rw-r--r-- | pgcli/pgclirc | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/pgcli/pgclirc b/pgcli/pgclirc index 51f7eae9..6fab747f 100644 --- a/pgcli/pgclirc +++ b/pgcli/pgclirc @@ -33,10 +33,11 @@ multi_line_mode = psql # "unconditional_update" will warn you of update statements that don't have a where clause destructive_warning = drop, shutdown, delete, truncate, alter, update, unconditional_update -# Destructive warning can restart the connection if this is enabled and the -# user declines. This means that any current uncommitted transaction can be -# aborted if the user doesn't want to proceed with a destructive_warning -# statement. +# When `destructive_warning` is on and the user declines to proceed with a +# destructive statement, the current transaction (if any) is left untouched, +# by default. When setting `destructive_warning_restarts_connection` to +# "True", the connection to the server is restarted. In that case, the +# transaction (if any) is rolled back. destructive_warning_restarts_connection = False # When this option is on (and if `destructive_warning` is not empty), |