I will also second that and if you got a lot of data, go for table partitioning as well but will not recommend dividing into different databases.
----------------- Shoaib Mir EnterpriseDB (www.enterprisedb.com) On 12/22/06, Vlad <[EMAIL PROTECTED]> wrote:
On 12/21/06, Ron Johnson <[EMAIL PROTECTED]> wrote: > > > >> Given the same physical hardware, which one is likely to perform > better? Does > >> it make any difference? Does using separate databases use more RAM > than a > >> single database with a bunch of different tables? > > Config files are global, so I doubt it. > if it's a web app with persistent connections, then splitting onto several databases may consume more RAM. Example: 100 apache clients connected to 3 databases creates 300 forked postmaster processes ; vs 100 apache clients connected to the same DB using three schemas only takes 100 postmasters -- Vlad
