Tom Lane wrote:
Bruce Momjian <[EMAIL PROTECTED]> writes:
Can we allow the IPv6 entries to be in pg_hba.conf but ignore them on
non-IPv6 machines, or allow the connection to fail?
I don't see a good way yet. The fly in the ointment is that HAVE_IPV6 is set by configure based on the capabilities of userland libraries; we cannot assume that HAVE_IPV6 means the kernel knows IPv6. But if we simply suppress failure messages on IPv6 addresses, we are going to create severe headaches for people who are actually using IPv6.
Ah, the joys of portability :-(
Anyone see a clean solution?
How about a 'localhost' keyword which would match the local host according to whatever ip stack(s) is (are) running? e.g.
localhost all all trust
Then we wouldn't have to play initdb tricks, but we would have to make postmaster a bit smarter.
Downside is pg_hba.conf seems to be rapidly becoming more complex.
cheers
andrew
---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
