[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [GENERAL] Schema's versus tablespace
From:       Dick Kniep <dick () kniep ! nl>
Date:       2006-03-28 7:56:20
Message-ID: 200603280956.20357.dick () kniep ! nl
[Download RAW message or body]

OK, that's cleared, thanks,

Now another question related to this. In 7.4.8 I have a schema with the 
following authorization:

CREATE SCHEMA adeuxproductie
  AUTHORIZATION postgres;
GRANT ALL ON SCHEMA adeuxproductie TO postgres;
GRANT ALL ON SCHEMA adeuxproductie TO GROUP adeuxproductie;
COMMENT ON SCHEMA adeuxproductie IS 'Standard production schema';

Now when I try to access the tables/views in the schema as a user that is NOT 
a member of the group adeuxproductie, I expect it to fail. However, access is 
granted as if there is no authorization specified.

Is this a bug, or do I misunderstand something?

Cheers,
Dick

On Tuesday 28 March 2006 09:48, Martijn van Oosterhout wrote:
> On Tue, Mar 28, 2006 at 09:41:46AM +0200, Dick Kniep wrote:
> > Hi list,
> >
> > We have developed a system that is running as an ASP application,
> > currently we are using Postgresql 7.4. For every customer we have a
> > separate schema, and this works OK. Now in version 8, tablespaces were
> > introduced. This summer we are planning to migrate to version 8.1.
> > Question is if there are advantages to use tablespaces instead of
> > schema's?
>
> Schemas related to how your tables are logically divided up.
> Tablespaces are about where the tables are actually stored on disk. As
> such they have nothing to do with eachother. You can mix and match as
> you please.
>
> Have a nice day,

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
[prev in list] [next in list] [prev in thread] [next in thread]