Re: proposal: psql: psql variable BACKEND_PID - Mailing list pgsql-hackers

From Andres Freund
Subject Re: proposal: psql: psql variable BACKEND_PID
Date
Msg-id 20230211210503.kqvno4iplx6lnalx@awork3.anarazel.de
Whole thread Raw
In response to Re: proposal: psql: psql variable BACKEND_PID  (Corey Huinker <corey.huinker@gmail.com>)
List pgsql-hackers
On 2023-02-04 15:35:58 -0500, Corey Huinker wrote:
> This effectively makes the %p prompt (which I use in the example above) the
> same as %:BACKEND_PID: and we may want to note that in the documentation.

I don't really see much of a point in noting this in the doc.  I don't know in
what situation a user would be helped by reading

+         This substitution is almost equal to using <literal>%:BACKEND_PID:</literal>,
+         but it is safer, because psql variable can be overwriten or unset.

or just about any reformulation of that?



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: refactoring relation extension and BufferAlloc(), faster COPY
Next
From: Andres Freund
Date:
Subject: Re: refactoring relation extension and BufferAlloc(), faster COPY