From 5050f01abce7aedd22e081588b4a057b207d31ce Mon Sep 17 00:00:00 2001 From: Damien Baty Date: Mon, 6 Nov 2023 07:10:47 +0100 Subject: pgclirc: Clarify description of `destructive_warning_restarts_connection` option (#1437) --- pgcli/pgclirc | 9 +++++---- 1 file 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), -- cgit v1.2.3