Hi,
On 2019-08-13 10:43:07 -0400, Tom Lane wrote:
> How would we get at that data without writing our own DNS client?
> (AFAIK, our existing DNS interactions are all handled by getnameinfo()
> or other library-supplied functions.)
> Maybe that'd be worth doing, but it sounds like a lot of work an
Feike Steenbergen writes:
> I'd like to get some feedback on whether or not implementing a DNS SRV feature
> for connecting to PostgreSQL would be desirable/useful.
How would we get at that data without writing our own DNS client?
(AFAIK, our existing DNS interactions are all handled by getnamein
On 13 Aug 2019, at 11:50, Feike Steenbergen wrote:
> I'd like to get some feedback on whether or not implementing a DNS SRV feature
> for connecting to PostgreSQL would be desirable/useful.
A big +1.
We currently use SRV records to tell postgresql what kind of server it is. This
way all of our
Hi all,
I'd like to get some feedback on whether or not implementing a DNS SRV feature
for connecting to PostgreSQL would be desirable/useful.
The main use case is to have a DNS SRV record that lists all the possible
primaries of a given replicated PostgreSQL cluster. With auto failover
solutions
