Re: Creation of a read-only role.
| От | Dmitry Koterov |
|---|---|
| Тема | Re: Creation of a read-only role. |
| Дата | |
| Msg-id | d7df81620703180159t515315bemf21f1c6daafb6bce@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Creation of a read-only role. ("hubert depesz lubaczewski" <depesz@gmail.com>) |
| Ответы |
Re: Creation of a read-only role.
|
| Список | pgsql-general |
> actually - you dont need the read-only role, if this is only for slave
> nodes. slony takes care about the issue and doesn't allow any writes
> on slaves.
Great!
But what about a role which can modify the data, but cannot modify the database schema?
> nodes. slony takes care about the issue and doesn't allow any writes
> on slaves.
Great!
But what about a role which can modify the data, but cannot modify the database schema?
On 3/17/07, hubert depesz lubaczewski <depesz@gmail.com> wrote:
On 3/16/07, Dmitry Koterov <dmitry@koterov.ru> wrote:
> Overall, we need 3 roles:
> 1. Administrator: can do anything with a database (by default this user is
> already exists - "postgres").
> 2. Read-only: can only read. Runs on all slave nodes.
actually - you dont need the read-only role, if this is only for slave
nodes. slony takes care about the issue and doesn't allow any writes
on slaves.
depesz
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
В списке pgsql-general по дате отправления: