Re: control pg_hba.conf via SQL

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Chris Browne <cbbrowne(at)acm(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: control pg_hba.conf via SQL
Date: 2006-03-30 18:27:25
Message-ID: 442C230D.8080706@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Chris Browne wrote:
>> Maybe we could do something like this: if there is a pg_hba.conf
>> file present, then use it as now and ignore the access rights table
>> - if someone does GRANT/REVOKE CONNECT while under pg_hba.conf then
>> process it but issue a warning. Maybe there could also be an initdb
>> switch that gave users a choice.
>>
>
> initdb is a terrible choice for that; that means you have to
> re-initialize the database to change the option.
>
>

Not at all. Where did you get that idea? Not everything set by initdb is
set in concrete. For example, initdb sets shared_buffers but you sure
don't need to rerun initdb to change that or anything else it sets in
postgresql.conf.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2006-03-30 18:38:26 Re: Index vacuum improvements
Previous Message Chris Browne 2006-03-30 17:46:12 Re: control pg_hba.conf via SQL