Re: Triggers and Multiple Schemas. - Mailing list pgsql-general

From Louis Gonzales
Subject Re: Triggers and Multiple Schemas.
Date
Msg-id 440F3F58.2010607@linuxlouis.net
Whole thread Raw
In response to Re: Triggers and Multiple Schemas.  (Scott Marlowe <smarlowe@g2switchworks.com>)
Responses Re: Triggers and Multiple Schemas.  (Scott Marlowe <smarlowe@g2switchworks.com>)
List pgsql-general
Scott Marlowe wrote:
<blockquote cite="mid1141849323.6249.9.camel@state.g2switchworks.com"
 type="cite">
  On Wed, 2006-03-08 at 14:19, Louis Gonzales wrote:



    Paul,
When you say "multiple identical schemas" are they all separate
explicit schemas?  Or are they all under a general 'public' schema.
From my understanding, when you create a new db instance, it's under
the public level schema by default unless you create an explicit
schema and subsequently a db instance - or several - therein,
effectively establishing sibling db instances belonging to a single
schema, I know at least that data in the form of table access is
allowed across the siblings.  I'd also assume that this would be the
case for triggers and functions that could be identified or defined at
the 'root' level



Ummm.  In PostgreSQL schemas are contained within databases, not the
other way around.  It's cluster contains databases contains schemas
contains objects (tables, sequences, indexes, et. al.)

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend


I stand corrected.  That's right.  But under a database you create your
explicit schemas, to organize tables which constitute your separate
data, where all of the schemas belonging to a database instance, can
share resources without conflicting with one another.

I apologize for giving the inaccurate description of database to schema
relationship.

pgsql-general by date:

Previous
From: Richard Huxton
Date:
Subject: Re: Out of memory error on pg_restore
Next
From: Scott Marlowe
Date:
Subject: Re: Triggers and Multiple Schemas.