From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Andrew Sullivan <ajs(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: TODO Item: Allow pg_hba.conf to specify host names along with IP addresses |
Date: | 2008-06-13 22:21:35 |
Message-ID: | 4852F2EF.2060901@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
>
>> Perhaps the solution to this problem is to do the lookups and store the
>> TTL of each answer. At the time of actually checking you need only get
>> a new answer for those that expired.
>>
>
> This is not behavior we'd want to put into the postmaster, though,
> and it's hard to see how to manage it otherwise. (Well, maybe a new
> postmaster child process just for this, but I find it hard to believe
> the feature is worth that.)
>
>
>
Indeed.
The only circumstance in which this feature should be used is probably
where you have control over the zones involved. For remote connections
I'd far rather have an open address specification and require SSL with
client side certs.
The potential for self-inflicted pain from this feature does worry me a bit.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2008-06-13 23:40:41 | Re: Options for protocol level cursors |
Previous Message | Tom Lane | 2008-06-13 21:50:38 | Re: TODO Item: Allow pg_hba.conf to specify host names along with IP addresses |