PGSQL GENERAL 45 BEST PRACTICE IN POSTGRES
From: nileshd@no-spam ("Nilesh Doshi")
Subject: Best practice in postgres
Date: Fri, 10 Dec 2004 14:49:30 -0800


Hi All,

I'm new to postgres, so I need your help.

We are in the process of migrating from oracle to postgres. DB size is about 400gb.
My question is about schemas in oracle and postgres. Does every schema in oracle becomes a separate database in postgres ? OR it is still like oracle, where all schemas are part of big database ?

Also, I thought vacuuming will be easier if oracle schema becomes database in postgres. For example in our case each schema is like 80-90 gb, smaller compare to vacuuming on 400gb.

Thanks,

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match



From: xzilla@no-spam (Robert Treat)
Subject: Re: Best practice in postgres
Date: 14 Dec 2004 09:29:25 -0500

On Fri, 2004-12-10 at 17:49, Nilesh Doshi wrote:
> Hi All,
> > I'm new to postgres, so I need your help.
> > We are in the process of migrating from oracle to postgres. DB size is about > 400gb.
> My question is about schemas in oracle and postgres. Does every schema in > oracle becomes a separate database in postgres ? OR it is still like oracle, > where all schemas are part of big database ?
>
I'm pretty sure you want schema -> schema and not schema -> database,
mainly because the semantics for querying across databases are much more cumbersome than querying across schemas. If you are not doing any cross schema work, then it probably doesn't matter as much.
Robert Treat -- Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html