Re: PGSERVICEFILE as part of a normal connection string

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>
To: Corey Huinker <corey.huinker@gmail.com>
Cc: Torsten Förtsch <tfoertsch123@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2025-01-27T05:00:54Z
Lists: pgsql-hackers
On Wed, Nov 20, 2024 at 02:58:43AM -0500, Corey Huinker wrote:
> Currently, a lot of our utility scripts (anything that uses
> connectDatabase) don't support service=name params or PGSERVICE=name env
> vars, which is really too bad. I previously thought that this was because
> of a lack of interest, but perhaps people do want it?

I'm all for more test coverage, FWIW.

Torsten, the patch has been waiting on input from you based on my
latest review for some time, so I have marked it as returned with
feedback in the CP app.  Feel free to resubmit a new version if you
are planning to work on that.

Thanks.
--
Michael

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. psql: Add variable SERVICEFILE

  2. libpq: Add "servicefile" connection option

  3. libpq: Add TAP test for nested service file

  4. libpq: Fix some issues in TAP tests for service files

  5. docs: Fix column count attribute in table

  6. libpq: Add TAP tests for service files and names