| From: | Niels Jespersen <NJN(at)dst(dot)dk> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | SV: Npgsql and the Connection Service File |
| Date: | 2021-01-30 15:56:18 |
| Message-ID: | 8c4a611e414844329eda224911871786@dst.dk |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>
>
>-----Oprindelig meddelelse-----
>Fra: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
>Sendt: 29. januar 2021 20:14
>Til: Niels Jespersen <NJN(at)dst(dot)dk>; pgsql-general(at)lists(dot)postgresql(dot)org
>Emne: Re: Npgsql and the Connection Service File
>
>On Fri, 2021-01-29 at 14:13 +0000, Niels Jespersen wrote:
>> Is there a way to get Npgsql understand the Connection Service File (https://www.postgresql.org/docs/13/libpq-pgservice.html) ?
>>
>> The purpose is to abstract physical details such as hostname, portnumber away from the application.
>
>No, the service file is part of libpq, and Npgsql doesn't use that.
>
Yes. Thank you for clarifying.
It would be nice if Npgsql (and jdbc and others) emulated the libpq behaviour. Because in my mind, abstracting hostname, portnumber and databasename away is a really useful feature.
How do others manage this?
Regards Niels Jespersen
>Yours,
>Laurenz Albe
>--
>Cybertec | https://www.cybertec-postgresql.com
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-01-30 16:50:14 | Re: Occasional lengthy locking causing stalling on commit |
| Previous Message | Ben Hoskings | 2021-01-30 14:07:31 | Occasional lengthy locking causing stalling on commit |