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
>
>
>
> 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
connectDatab
On Mon, Nov 18, 2024 at 09:21:56PM +0100, Torsten Förtsch wrote:
> I like to bundle all my database connections in a .pg_service.conf. Over
> time I collected a bunch of such service files. A while back I discovered
> that the service file can only be specified as an environment variable. It
> cann
On Mon, 2024-11-18 at 21:21 +0100, Torsten Förtsch wrote:
> I like to bundle all my database connections in a .pg_service.conf. Over time
> I
> collected a bunch of such service files. A while back I discovered that the
> service file can only be specified as an environment variable. It cannot be
Hi,
I like to bundle all my database connections in a .pg_service.conf. Over
time I collected a bunch of such service files. A while back I discovered
that the service file can only be specified as an environment variable. It
cannot be given as part of the connection string like
psql "service=$MY
