ISTM that the first requirement is for a sane API that will handle the
fact that HBA lines are ordered. Persistence in itself shouldn't be a
big problem - we already do that with some shared tables, iirc.
so we might have some functions like:
insert_hba_rule(at_position int, connection_type text, username text,
dbname text, cidr_host text, method text)
move_hba_rule(from_position int, to_position int)
delete_hba_rule(at_position int)
Inventing new SQL syntax might make things a bit tougher.
cheers
andrew
Jonah H. Harris wrote:
I'd like to expand this idea with this TODO item. If this is already
on the TODO, please disregard. I'm thinking something like the
following:
Enable the alteration and persistence of postgresql.conf and
pg_hba.conf configuration parameters via SQL.
On 3/29/06, BERTHOULE Emmanuel <[EMAIL PROTECTED]> wrote:
Hi all,
i would like to work on control setting pg_hba.conf via SQL....( cf TODO
List ), and i would know if the pg_hda.conf must be replaced by pg_hba
table ?
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
