| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | proposal: psql: psql variable BACKEND_PID |
| Date: | 2023-02-03 10:41:29 |
| Message-ID: | CAFj8pRBaSVj-8yXcMwKaF7ABx1kYSyUHRM4BdLxoQwf0+RfGsw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-implementation-of-BACKEND_PID-psql-s-variable.patch | text/x-patch | 1.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2023-02-03 11:52:27 | Re: Time delayed LR (WAS Re: logical replication restrictions) |
| Previous Message | Pavel Borisov | 2023-02-03 10:39:31 | Re: [PATCH] Compression dictionaries for JSONB |