| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | songjinzhou <tsinghualucky912(at)foxmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Japin Li <japinli(at)hotmail(dot)com> |
| Subject: | Re: libpq: Add PQapplicationname() function |
| Date: | 2025-04-29 15:27:05 |
| Message-ID: | CAKFQuwZucqaCncNFGqEzYnP2WWonEDv-uR2ycA1LCoAg=No5Tw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tuesday, April 29, 2025, songjinzhou <tsinghualucky912(at)foxmail(dot)com>
wrote:
> Dear hackers, here is a libpq function: PQapplicationname(), I think it
> may be of some use.
>
You really should provide at least one reasoned use case for why this
should exist.
>
> Looking forward to your reply, thank you.
>
>
This isn’t even the correct code to use for this. PQparameterStatus is
where you’d access application_name. I don’t see a good reason in
providing multiple ways to get access to the same data value.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Euler Taveira | 2025-04-29 15:37:17 | Re: Disallow redundant indexes |
| Previous Message | Tom Lane | 2025-04-29 15:16:59 | Re: What's our minimum supported Python version? |