Re: libpq should not look up all host addresses at once

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Garick Hamlin <ghamlin(at)isc(dot)upenn(dot)edu>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: libpq should not look up all host addresses at once
Date: 2018-08-14 20:53:48
Message-ID: alpine.DEB.2.21.1808142245570.24283@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Hello Garick,

>> I read the rational of the host/hostaddr artificial mapping. I cannot say
>> I'm thrilled with the result: I do not really see a setting where avoiding a
>> DNS query is required but which still needs a hostname for auth... If you
>> have GSSAPI or SSPI then you have an underlying network, in which a dns
>> query should be fine.
>
> FWIW, I think this is useful even it will be uncommon to use. I run
> some HA services here and I find I use this kind of functionality all
> the time to test if a standby node functioning properly.

Ok, I understand that you want to locally override DNS results for
testing purposes. Interesting use case.

> Anyway, if it's not a big burden, I suggest you keep it, IIUC.

I would not suggest to remove the feature, esp if there is a reasonable
use case.

> This kind of thing is really handy especially since today's cloudy-stuff
> means one often gets all-the-nat whether one wants it or not.

Yep, NAT, another possible use case.

So it is a useful feature for specialized use cases! I just lack
imagination:-) Thanks for the explanations.

Maybe I'll try to just improve the the documentation.

--
Fabien.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonathan S. Katz 2018-08-14 21:06:31 Re: Expression errors with "FOR UPDATE" and postgres_fdw with partition wise join enabled.
Previous Message Alvaro Herrera 2018-08-14 20:53:11 Re: [HACKERS] pgbench - allow to store select results into variables