Re: PGSERVICEFILE as part of a normal connection string
Corey Huinker <corey.huinker@gmail.com>
From: Corey Huinker <corey.huinker@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Torsten Förtsch <tfoertsch123@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2024-11-20T07:58:43Z
Lists: pgsql-hackers
> > > > Interesting. We've never had tests for that even for "service". > Perhaps it would be the time to add some tests for the existing case > and the one you are adding? Your test suite should make that easy to > add. > 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?
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