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 →
-
psql: Add variable SERVICEFILE
- 6b1c4d326b06 19 (unreleased) landed
-
libpq: Add "servicefile" connection option
- 092f3c63efc6 19 (unreleased) landed
-
libpq: Add TAP test for nested service file
- df286a5b830a 19 (unreleased) landed
-
libpq: Fix some issues in TAP tests for service files
- 2c7bd2ba507e 18.0 landed
-
docs: Fix column count attribute in table
- ea3f9b6da34a 18.0 cited
-
libpq: Add TAP tests for service files and names
- 72c2f36d5727 18.0 landed