Re: Thoughts on a "global" client configuration?
Peter Eisentraut <peter@eisentraut.org>
From: Peter Eisentraut <peter@eisentraut.org>
To: Jacob Champion <jacob.champion@enterprisedb.com>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2025-10-15T19:20:31Z
Lists: pgsql-hackers
On 06.10.25 20:05, Jacob Champion wrote: > I started on a proof of concept and very quickly hit a fork. Do I > 1) introduce a completely new config file, or > 2) adapt pg_service.conf to this use case? I've been thinking about this kind of thing for a long time, and my intuition has always been to have some kind of [default] section in pg_service.conf. That would probably be relatively easy. But: > - backwards and forwards compatibility (we don't ever break old > libpqs, but new libpqs can add new options safely) It might be worth elaborating exactly how this would be solved. If I look through my dotfiles history, this kind of thing has been a perennial problem. I don't have any specific ideas right now -- other than perhaps "ignore unknown parameters", which is surely not without problems. Depending on what we'd settle on here, that might inform whether it's feasible to stick this into pg_service.conf or whether it needs to be a separate thing.