Re: host name support in pg_hba.conf

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: host name support in pg_hba.conf
Date: 2010-10-13 19:37:03
Message-ID: 1286998623.4671.18.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On tis, 2010-10-12 at 17:03 -0400, Tom Lane wrote:
> Oh, I had an idea for a small improvement to this. It doesn't seem
> unlikely that pg_hba.conf could contain multiple entries with the same
> host name (but, presumably, different user and/or database names). As
> this is coded, you'll do a forward DNS lookup for each one until
> finding
> the complete match. You could easily prevent that by adding an
> additional cache field to struct Port, along the lines of
> +1 = remote_hostname is known to resolve to client's IP
> address
> -1 = remote_hostname is known NOT to resolve to client's IP
> address
> 0 = we have not done the forward DNS lookup yet.
> With this additional field we could guarantee to do not more than two
> DNS lookups per connection attempt.

That's a very good idea. I will revise my patch.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message david 2010-10-13 19:37:45 Re: Slow count(*) again...
Previous Message Sergey Burladyan 2010-10-13 19:36:08 FreeBSD 8.0 i386, plpythonu, threaded Python not supported on this platform