Re: Regrading TODO item alerting pg_hba.conf from SQL

From: "Sander Steffann" <s(dot)steffann(at)computel(dot)nl>
To: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Regrading TODO item alerting pg_hba.conf from SQL
Date: 2006-04-16 23:32:45
Message-ID: 005101c661ae$111f1010$64c8a8c0@balefirehome
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

Tom Lane writes:
> Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
>> For simple systems then you could have a short pg_hba.conf to limit the
>> IP addresses users can connect on, and the DB stores what databases
>> they have access to...
>
> Right, you'd still have a pg_hba.conf, but it would hopefully be short
> and sweet, not doing much more than listing which addresses you want
> to allow connections from and what the authentication mechanisms ought
> to be.

From another message from Tom:
>> How would you suggest the SQL syntax be like for example.
>
> Just another privilege name in the existing GRANT/REVOKE ON DATABASE
> syntax.

Sounds like a good idea to me. Make pg_hba.conf simpler and administered by
the admin, and give the database owner the tools to decide who gets to
connect.

Nice!
Sander

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Brown 2006-04-17 02:29:43 Corrupt data pages...
Previous Message Robert Treat 2006-04-16 23:06:33 Re: Google Summer of Code (Fix aggregate operators & Implement features such as Data Cubes and Skyline)