From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: Use "samehost" by default in pg_hba.conf? |
Date: | 2009-10-01 03:16:13 |
Message-ID: | 8079.1254366973@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> I'm not sure if it out-ranks the advantages of the change for buildfarm
> support, but the above change isn't actually without any disadvantage.
> Specifically, not every auth mechanism that works with -h machine_name
> works with -h localhost, but the first record in pg_hba which is matched
> is used. I could have:
> host all all 127.0.0.1/32 @authmethod@
> host all all A.B.C.D/32 @authmethod2@
If you've got any such thing, you've got a *nondefault* pg_hba.conf
file. Or are you opining that people who are smart enough to set
that up are too stupid to replace a single "samehost" entry with
the two entries they need?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2009-10-01 03:17:30 | Re: [PATCH] Reworks for Access Control facilities (r2311) |
Previous Message | KaiGai Kohei | 2009-10-01 03:10:47 | Re: [PATCH] Reworks for Access Control facilities (r2311) |