| From: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: proposal: psql: psql variable BACKEND_PID |
| Date: | 2023-02-03 19:27:23 |
| Message-ID: | CADkLM=fQUAGG2WXO3_2Qci+-nR3URmzi0E03Wvizwg71MORwvg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Feb 3, 2023 at 5:42 AM Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
wrote:
> Hi
>
> We can simply allow an access to backend process id thru psql variable. I
> propose the name "BACKEND_PID". The advantages of usage are simple
> accessibility by command \set, and less typing then using function
> pg_backend_pid, because psql variables are supported by tab complete
> routine. Implementation is very simple, because we can use the function
> PQbackendPID.
>
> Comments, notes?
>
> Regards
>
> Pavel
>
Interesting, and probably useful.
It needs a corresponding line in UnsyncVariables():
SetVariable(pset.vars, "BACKEND_PID", NULL);
That will set the variable back to null when the connection goes away.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-02-03 19:32:39 | First draft of back-branch release notes is done |
| Previous Message | Nathan Bossart | 2023-02-03 18:54:17 | Re: Weird failure with latches in curculio on v15 |