From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
---|---|
To: | Jay Greenfield <jag(at)timberline(dot)ca> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Postgres slower than MS ACCESS |
Date: | 2006-02-14 16:04:45 |
Message-ID: | 1139933084.22740.177.camel@state.g2switchworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Tue, 2006-02-14 at 09:51, Jay Greenfield wrote:
> I am running some simple queries to benchmark Postgres 8.1 against MS
> Access and Postgres is 2 to 3 times slower that Access.
A BUNCH OF STUFF SNIPPED
> Why does Access run so much faster? How can I get Postgres to run as
> fast as Access?
Because Access is not a multi-user database management system designed
to handle anywhere from a couple to several thousand users at the same
time?
PostgreSQL can do this update while still allowing users to access the
data in the database, and can handle updates to the same table at the
same time, as long as they aren't hitting the same rows.
They're two entirely different beasts.
One is good at batch processing moderate amounts of data for one user at
a time. The other is good for real time processing of very large
amounts of data for a fairly large number of users while running at an
acceptable, if slower speed.
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2006-02-14 16:06:41 | Re: out of memory |
Previous Message | martial.bizel | 2006-02-14 16:03:38 | Re: out of memory |