Skip site navigation (1) Skip section navigation (2)

Re: control pg_hba.conf via SQL

From: Svenne Krap <svenne(at)krap(dot)dk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>,"Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>,BERTHOULE Emmanuel <pgdev(at)manberth(dot)homeip(dot)net>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: control pg_hba.conf via SQL
Date: 2006-03-30 08:12:46
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Tom Lane wrote:
> I'm a bit suspicious of proposals that we move either hba or conf into
> SQL tables --- one of the main reasons why they are flat files is so
> you can still edit them after you've hosed them to the point that the
> database won't start or won't let you in.  If you don't have a non-kluge
> solution to the DBA-mistake-recovery scenario, this is not going to be
> an improvement.
What about a line in pg_hba which tells pgsql how to handle it. I.e. an 
example  is :

--- pg_hba.conf ---
Include_file = {only, first, last, not}
< normal lines >
--- pg_hba.conf ---

Not means only use in DB data.
First means load file before data from DB (so db can overwrite file 
Last means load file after data from DB (so file can overwrite db settings)
Only means just use file settings (as today)
If the line is missing, assume only (backwards compatibility).

By the way, I really think there should be real grammar for it, not just 
a couple of sql helper functions.


In response to

pgsql-hackers by date

Next:From: Magnus HaganderDate: 2006-03-30 08:26:44
Subject: Re: Initdb on Windows 2003
Previous:From: Simon RiggsDate: 2006-03-30 07:54:17
Subject: Re: control pg_hba.conf via SQL

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group