public inbox for [email protected]
help / color / mirror / Atom feedFrom: Andrew Sullivan <[email protected]>
To: [email protected]
Subject: Re: PostgreSQL vs. MySQL
Date: Fri, 4 Jul 2003 10:28:00 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <01bf01c34235$a4c8aa60$01000001@trouble>
References: <[email protected]>
<01bf01c34235$a4c8aa60$01000001@trouble>
On Fri, Jul 04, 2003 at 10:07:46AM -0400, Brian Tarbox wrote:
> 512 mb memory, latest production versions of each database. By vanilla
> RedHat I mean that I installed RH on a clean system, said install everything
> and did no customization of RH settings.
Does that include no customization of the Postgres settings?
> We had about 40 tables in the db, with joined queries on about 8-12 tables.
SELECTs only? because. . .
> of records. There were indexes on all join fields, and all join fields were
> listed as foriegn keys. All join fields were unique primary keys in their
. . .you know that FK constraints in Postgres are not cheap, right?
> I did no tuning of MySql. The only tuning for PG was to vacuum and vacuum
> analyze.
This appears to be a "yes" answer to my question above. Out of the
box, PostgreSQL is set up to be able to run on a 1992-vintage SGI
Indy with 8 M of RAM (ok, I may be exaggerating, but only by a bit);
it is not tuned for performance. Running without even tweaking the
shared buffers is guaranteed to get you lousy performance.
A
--
----
Andrew Sullivan 204-4141 Yonge Street
Liberty RMS Toronto, Ontario Canada
<[email protected]> M2P 2A8
+1 416 646 3304 x110
view thread (66+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: PostgreSQL vs. MySQL
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox