SV: Npgsql and the Connection Service File - Mailing list pgsql-general

From Niels Jespersen
Subject SV: Npgsql and the Connection Service File
Date
Msg-id 8c4a611e414844329eda224911871786@dst.dk
Whole thread Raw
In response to Re: Npgsql and the Connection Service File  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: SV: Npgsql and the Connection Service File  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-general
>
>
>-----Oprindelig meddelelse-----
>Fra: Laurenz Albe <laurenz.albe@cybertec.at> 
>Sendt: 29. januar 2021 20:14
>Til: Niels Jespersen <NJN@dst.dk>; pgsql-general@lists.postgresql.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
>

pgsql-general by date:

Previous
From: Ben Hoskings
Date:
Subject: Occasional lengthy locking causing stalling on commit
Next
From: Tom Lane
Date:
Subject: Re: Occasional lengthy locking causing stalling on commit