| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Can we have a new SQL callable function to get Postmaster PID? |
| Date: | 2021-02-04 06:51:26 |
| Message-ID: | YBuZbmWCZ7xnKU8R@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Feb 04, 2021 at 11:30:09AM +0530, Bharath Rupireddy wrote:
> But sometimes we may also have to debug postmaster code, on different
> platforms maybe. I don't know how the postmaster pid from the user
> perspective will be useful in customer environments and I can't think
> of other usages of the pg_postgres_pid().
I had the same question as Tomas in mind when reading this thread, and
the use case you are mentioning sounds limited to me. Please note
that you can already get this information by using pg_read_file() on
postmaster.pid so I see no need for an extra function.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-02-04 06:54:29 | Re: Removing support for COPY FROM STDIN in protocol version 2 |
| Previous Message | Michael Paquier | 2021-02-04 06:38:39 | Re: Allow CLUSTER, VACUUM FULL and REINDEX to change tablespace on the fly |