[postgis-users] Basic question #3 schemas

Ben Madin ben at remoteinformation.com.au
Thu Feb 19 15:47:20 PST 2009

G'day Kevin,

thank you very much for this - can I just clarify:

When you install a new PostGIS, you install the 'current' postgis into  
the public schema, but all your data & functions into other schemas;

or do you create a schema for postgis (again separate from the public  
and your other 'application specific' schemas?



On 20/02/2009, at 5:01 AM, postgis-users- 
request at postgis.refractions.net wrote:

> Date: Wed, 18 Feb 2009 20:09:42 -0800
> From: Kevin Neufeld <kneufeld at refractions.net>
> Subject: Re: [postgis-users] Basic question #3 schemas
> It's highly recommended to use schemas.  No, there aren't any concerns
> with speed or indexing that I'm aware of.
> I have about 50 schemas in a large 150GB database at the moment.  Each
> schema is like a subdirectory of tables.  Once you're in the habit to
> schema-qualify your tables or get familiar with using search_paths,  
> it's
> exactly like using the single public schema ... except now your data  
> is
> organized.
> Personally, I take it a step further.  I never store anything in the
> public schema - I reserve that for PostGIS and PostgreSQL modules like
> cube or tsearch.  It makes upgrading crazy easy because I can pg_dump
> everything EXCEPT the public schema into a new PostGIS install.   
> Besides
> having hundreds of tables, I also have many custom plpgsql functions.
> If I stored them in public, they would get mixed up with the 600+
> PostGIS functions.  I would need to sort them all out when trying to
> pg_dump everything except PostGIS ... now that's would be a pain.
> Cheers,
> Kevin


Ben Madin

t : +61 8 9192 5455
f : +61 8 9192 5535
m : 0448 887 220
Broome   WA   6725

ben at remoteinformation.com.au

							Out here, it pays to know...

More information about the postgis-users mailing list