Skip to content

Conversation

@feikesteenbergen
Copy link

The whole point of supporting this can best be said by directly quoting
the PostgreSQL manual:

The connection service file allows libpq connection parameters to be
associated with a single service name. That service name can then be
specified by a libpq connection, and the associated settings will be
used. This allows connection parameters to be modified without
requiring a recompile of the libpq application. The service name can
also be specified using the PGSERVICE environment variable.

source: https://www.postgresql.org/docs/current/libpq-pgservice.html

Fixes #538

The whole point of supporting this can best be said by directly quoting
the PostgreSQL manual:

> The connection service file allows libpq connection parameters to be
> associated with a single service name. That service name can then be
> specified by a libpq connection, and the associated settings will be
> used. This allows connection parameters to be modified without
> requiring a recompile of the libpq application. The service name can
> also be specified using the PGSERVICE environment variable.

source: https://www.postgresql.org/docs/current/libpq-pgservice.html

Fixes lib#538
@ribasushi
Copy link

@rafiss ping on this PR? Seems pretty decent.

The alternative today is to use something like this, which I have to admit is pretty gross... https://github.com/behrang/go-pgservice

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Implement Connection Service File

2 participants