pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joshua D. Drake <jd@commandprompt.com>
To: Andrew Sullivan <ajs@crankycanuck.ca>
Cc: pgsql-hackers@postgresql.org
Subject: Re: function body actors (was: [PERFORM] viewing source code)
Date: Fri, 21 Dec 2007 14:07:08 -0800
Message-ID: <20071221140708.289f796f@commandprompt.com> (raw)
In-Reply-To: <20071221214746.GG3864@crankycanuck.ca>
References: <b42b73150712202109u26d05d01q4f1b8be8d29f763c@mail.gmail.com>
	<26811.1198215605@sss.pgh.pa.us>
	<20071221164826.GI10918@crankycanuck.ca>
	<b42b73150712210948g42498150h976c0b972d632faa@mail.gmail.com>
	<10257.1198263464@sss.pgh.pa.us>
	<20071221205619.GD3864@crankycanuck.ca>
	<12277.1198271991@sss.pgh.pa.us>
	<20071221214746.GG3864@crankycanuck.ca>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 21 Dec 2007 16:47:46 -0500
Andrew Sullivan <ajs@crankycanuck.ca> wrote:

> On Fri, Dec 21, 2007 at 04:19:51PM -0500, Tom Lane wrote:
> > > 2.	Protect the content of a field from _some_ users on a
> > > given system,
> > 
> > I would argue that (2) is reasonably well served today by setting up
> > separate databases for separate users. 
> 
> I thought actually this was one of the use-cases we were hearing.
> Different people using the same database (because the same data),
> with rules about the different staff being able to see this or that
> function body.  I can easily imagine such a case, for instance, in a
> large organization with different departments and different
> responsibilities.  It seems a shame that the only answer we have
> there is, "Give them different databases."  

I think there is a fundamental disconnect here. The "Give them
different databases" argument is essentially useless. Consider a
organization that has Sales and HR.

You don't give both a separate database. They need access to "some" of
each others information. Just not all.

Sincerely,

Joshua D. Drake

- -- 
The PostgreSQL Company: Since 1997, http://www.commandprompt.com/ 
Sales/Support: +1.503.667.4564   24x7/Emergency: +1.800.492.2240
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
SELECT 'Training', 'Consulting' FROM vendor WHERE name = 'CMD'


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHbDkOATb/zqfZUUQRAqzmAJ9VhNXYtr/N7px3/iUenUJN+7r9jQCfQtj+
Hyfo4fLGrBGUN4jJcSgZEh0=
=xeLs
-----END PGP SIGNATURE-----


view thread (8+ messages)

Message-ID: <20071221140708.289f796f@commandprompt.com>
Permalink:  ../20071221140708.289f796f@commandprompt.com/
Also on:    postgresql.org/message-id/20071221140708.289f796f@commandprompt.com

 · 

reply

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-performance@postgresql.org
  Cc: jd@commandprompt.com, ajs@crankycanuck.ca, pgsql-hackers@postgresql.org
  Subject: Re: function body actors (was: [PERFORM] viewing source code)
  In-Reply-To: <20071221140708.289f796f@commandprompt.com>

* 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