From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | francois(dot)grandvarlet(at)wanadoo(dot)fr, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #17020: meta command psql \reset does not clear the query buffer |
Date: | 2021-05-19 14:39:32 |
Message-ID: | 20210519143932.GA24077@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2021-05-19 14:42:11 | Re: BUG #17023: wal_log_hints not configured even if it on |
Previous Message | Daniel Gustafsson | 2021-05-19 12:21:25 | Re: BUG #17024: ERROR: column c.relhasoids does not exist at character 245 |