Re: PG 14 release notes, first draft

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PG 14 release notes, first draft
Date: 2021-05-10 06:16:16
Message-ID: 6f6405dcffc01da2ee0aac112873e8e5ad66cc79.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 2021-05-10 at 02:03 -0400, Bruce Momjian wrote:
> When using \e in psql, if the buffer is not modified by the editor, ignore the editor contents and leave the buffer unchanged (Laurenz Albe)
> The \ef and \ev commands also now have this behavior. DOCS SAY BUFFER IS CLEARED.

It's a bit more complicated: If you edit the current buffer with \e, the buffer is
unchanged if you quit the editor.
However, if you edit the previous statement, a file or the definition of a function
or view, the query buffer is cleared if you quit the editor without saving.

Suggested wording:

When editing anything else than the current query buffer with \e, and you quit
the editor, the query buffer is cleared. This makes the behavior less surprising
and prevents the unintended re-execution of the previous statement.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2021-05-10 06:17:28 Re: Inaccurate error message when set fdw batch_size to 0
Previous Message Peter Smith 2021-05-10 06:15:06 Re: AlterSubscription_refresh "wrconn" wrong variable?