From: Tom Lane <tgl@sss.pgh.pa.us>
To: francois.grandvarlet@wanadoo.fr
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17020: meta command psql \reset does not clear the query
 buffer
In-reply-to: <17020-f5e23166506e7932@postgresql.org>
References: <17020-f5e23166506e7932@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Tue, 18 May 2021 22:16:16 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3429976.1621435359.1@sss.pgh.pa.us>
Date: Wed, 19 May 2021 10:42:39 -0400
Message-ID: <3429977.1621435359@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3429977.1621435359%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> issuing a command like : SELECT * FROM generate_series (1, 1000);
> meta command \p shows the query buffer
> meta command \reset tells "Query buffer reset (cleared)."
> but meta command \p still shows the query buffer and meta command \g execute
> the query
> Is this the normal behavior ?

Yes.  \p is documented as

    Print the current query buffer to the standard output. If the current
    query buffer is empty, the most recently executed query is printed
    instead.

and \g likewise says "If the current query buffer is empty, the most
recently sent query is re-executed instead".

> It seems to me that the query buffer should be empty after issuing \reset

It is.  If you now type something, that something is a new command that's
not concatenated with what you typed before.

			regards, tom lane