Andrew Dunstan wrote:
> >Bruce and I were just discussing this on the phone. It seems we have
> >two basic approaches to problem #2. Either we hack the postmaster so
> >that it will swallow IPv6 addresses in pg_hba.conf even without any real
> >IPv6 support, or we make the default pg_hba.conf contents different.
> >Neither of these is real pretty, but I am leaning to the second, because
> >I agree with your feeling that silently ignoring config lines is a bad
> >idea.
> >
> OK, now we are getting somewhere. I see that this would work. It's a bit
> ugly, though - with this plan the sample file in both CVS and the
> installation won't necessarily be what actually get put in place. What
> if some clever installer/administrator deliberately alters their
> installed sample file?
>
> Could we get the configure script to do it instead, since it too should
> know about ip6 capability? (I guess then we'd have
> pg_hba.conf.sample.in). That strikes me as being a lot cleaner.
I talked to Tom about this, and we clearly can do it as part of the
build process, rather than at initdb. Tom said postgresql.conf already
doesn't match the sample file because of changes made by initdb, so he
didn't see how pg_hba.conf changing during initdb would be any worse.
I think either way is fine. I prefer at build, but I can see his point
too.
-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610)
359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square,
Pennsylvania19073
