Date: Wed, 19 May 2021 10:39:32 -0400
From: Bruce Momjian <bruce@momjian.us>
To: francois.grandvarlet@wanadoo.fr, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17020: meta command psql \reset does not clear the query
 buffer
Message-ID: <20210519143932.GA24077@momjian.us>
References: <17020-f5e23166506e7932@postgresql.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <17020-f5e23166506e7932@postgresql.org>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: 
 <https://www.postgresql.org/message-id/20210519143932.GA24077%40momjian.us>
Precedence: bulk

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.grandvarlet@wanadoo.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@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

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