Re: Creation of a read-only role.

From: "Dmitry Koterov" <dmitry(at)koterov(dot)ru>
To: "hubert depesz lubaczewski" <depesz(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Creation of a read-only role.
Date: 2007-03-18 08:59:10
Message-ID: d7df81620703180159t515315bemf21f1c6daafb6bce@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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?

On 3/17/07, hubert depesz lubaczewski <depesz(at)gmail(dot)com> wrote:
>
> On 3/16/07, Dmitry Koterov <dmitry(at)koterov(dot)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
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dmitry Koterov 2007-03-18 09:02:32 Re: Creation of a read-only role.
Previous Message hubert depesz lubaczewski 2007-03-18 07:33:45 Re: Practical question.