RE: BUG #17020: meta command psql \reset does not clear the query buffer

Thank you very much for your answer and your explanations.
I should have read the doc more carefully.

Best regards,
François Grandvarlet

-----Message d'origine-----
De : Bruce Momjian <bruce(at)momjian(dot)us>
Envoyé : mercredi 19 mai 2021 16:40
À : francois(dot)grandvarlet(at)wanadoo(dot)fr; pgsql-bugs(at)lists(dot)postgresql(dot)org
Objet : Re: BUG #17020: meta command psql \reset does not clear the query
buffer

On Tue, May 18, 2021 at 10:16:16PM +0000, PG Bug reporting form wrote:
> The following bug has been logged on the website:
>
> Bug reference: 17020
> Logged by: François Grandvarlet
> Email address: francois(dot)grandvarlet(at)wanadoo(dot)fr
> PostgreSQL version: 13.3
> Operating system: Centos 7
> Description:
>
> Connected via psql
> 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 ?
> It seems to me that the query buffer should be empty after issuing
> \reset

I was recently confused by this too, but the psql \print documentation
clarified it for me:

\p or \print
Print the current query buffer to the standard output. If the
--> current query buffer is empty, the most recently executed query
is
--> printed instead.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

If only the physical world exists, free will is an illusion.