Re: Does "correlation" mislead the optimizer on large

From: Noah Silverman <noah(at)allresearch(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Does "correlation" mislead the optimizer on large
Date: 2003-01-24 21:55:45
Message-ID: 975BA89C-2FE6-11D7-A3A3-000393AA8F3C@allresearch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Hi!

Another fun question in our ongoing analysis on whether to switch from
mysql to postgres. (Just as an update, Postgres has performed
flawlessly on all of our stress tests so far.)

We have a situation where we will be creating two fairly large and
complex databases with many tables (thousands) each. From what I
understand, postgres keeps everything in one big data directory.

Would there be an advantage to putting each of the two databases into a
separate directory and starting two instances of postgres? Is it
better to just lump everything together.

In a perfect world, we would buy another database server and raid for
the second database, but being a small company, we just don't have the
budget right now. The raid on our current server is much bigger than we
need.

Thanks,

-N

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Noah Silverman 2003-01-24 22:39:42 Multiple databases one directory
Previous Message Tom Lane 2003-01-24 21:01:41 Re: Having trouble with backups (was: Re: Crash Recovery)