Re: Problem with reloading groups in pg_hba.conf

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Problem with reloading groups in pg_hba.conf
Date: 2002-03-22 17:34:38
Message-ID: Pine.LNX.4.30.0203221232180.787-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian writes:

> I don't know. Automatically modifying a manually maintained config file
> isn't too common a feature. One problem would be if you where modifying
> the file in your editor and the backend rewrote the file.

That's not different from you modifying the file in your editor and
someone else doing the same thing at the same time. Yes, the concurrency
issues are not trivial, but they can be solved.

> I think groups will give use the ability to add/remove connection from
> within the database. You just need to mention the group name in the
> config file. My original idea was to automatically identify some group
> name for each database but maybe that is too smart.

Yes, that is perfectly fine. I just want an additional interface that
allows you to "mention the group name in the config file" while connected
to the database.

--
Peter Eisentraut peter_e(at)gmx(dot)net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-03-22 17:38:30 Re: Problem with reloading groups in pg_hba.conf
Previous Message Tom Lane 2002-03-22 17:24:59 Re: Problem with reloading groups in pg_hba.conf