Problems with user-level security

Поиск
Список
Период
Сортировка
От Nick Sayer
Тема Problems with user-level security
Дата
Msg-id 1709.66.126.254.34.1005099567.squirrel@medusa.kfu.com
обсуждение исходный текст
Ответы Re: Problems with user-level security  (Stephan Szabo <sszabo@megazone23.bigpanda.com>)
Re: Problems with user-level security  (Peter Eisentraut <peter_e@gmx.net>)
Re: Problems with user-level security  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Problems with user-level security  ("Chad R. Larson" <chad@eldocomp.com>)
Список pgsql-admin
Maybe it's just me, but I think pg_hba.conf needs a user column in it.

On the one hand, I need

local sameuser password

because I have untrusted users who should only have access to their own
databases.

On the other hand, I do a nightly pg_dumpall as part of the backups so that
I don't have to dump the actual database working areas. For that to work, I
need to say

local all password

so that my backup script will work.

What I *really* want is for an extra column to be added to pg_hba.conf to
specify the user of interest. Like this:

all     local sameuser password
backups local all      password
pgsql   local all      password

Does this make any sense? Is there some way to achieve this I am missing?
The only way I can do backups at the moment is introduce a race condition
so that anyone can connect to any database they like at certain times of
day. Not good.






В списке pgsql-admin по дате отправления:

Предыдущее
От: "Sean K. Sell"
Дата:
Сообщение: Re: update in rule
Следующее
От: "Sean K. Sell"
Дата:
Сообщение: Re: Problems with user-level security