Re: Providing catalog view to pg_hba.conf file - Patch submission
От | Robert Haas |
---|---|
Тема | Re: Providing catalog view to pg_hba.conf file - Patch submission |
Дата | |
Msg-id | CA+TgmoafgMM5eP-RDFor9R51BFL7eX8cV9kzSbyMx-WnBudkYA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Providing catalog view to pg_hba.conf file - Patch submission (Greg Stark <stark@mit.edu>) |
Ответы |
Re: Providing catalog view to pg_hba.conf file - Patch
submission
|
Список | pgsql-hackers |
On Wed, Mar 11, 2015 at 1:32 PM, Greg Stark <stark@mit.edu> wrote: > I think what we have here is already a good semantic representation. It > doesn't handle all the corner cases but those corner cases are a) very > unlikely and b) easy to check for. A tool can check for any users starting > with + or named "all" or any databases called "sameuser" or "samerole". If > they exist then the view isn't good enough to reconstruct the raw file. But > they're very unlikely to exist, I've never heard of anyone with such things > and can't imagine why someone would make them. -1. Like Peter, I think this is a bad plan. Somebody looking at the view should be able to understand with 100% confidence, and without additional parsing, what the semantics of the pg_hba.conf file are. Saying "those cases are unlikely so we're not going to handle them" is really selling ourselves short. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: