From: Mark Felder <feld@feld.me>
To: pgsql-admin@postgresql.org
Subject: Re: pgadmin user access control features
Date: Tue, 04 Jan 2011 13:39:54 -0600
Message-ID: <op.vost8ru534t2sn@tech304> (raw)
In-Reply-To: <24001946.1624.1294160696171.JavaMail.root@mail.nextwavesys.com>
References: <24001946.1624.1294160696171.JavaMail.root@mail.nextwavesys.com>
On Tue, 04 Jan 2011 11:04:56 -0600, Dan Sabin <dan.sabin@nextwavesys.com>
wrote:
> The two options are to give them a query tool we design so we can
> restrict their actions (to prevent the database from being screwed up).
If their user still has access to doing other things it might be possible
for that data to be modified using regular postgres tools, which is a a
security risk of sorts. Perhaps it might be best for you to setup certain
functions or stored procedures that their database user only has access
to? I assume this is possible, anyway.
Regards,
Mark
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: feld@feld.me
Subject: Re: pgadmin user access control features
In-Reply-To: <op.vost8ru534t2sn@tech304>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox