Is it possible to configure Postgres to behave like Access - a single user and use as much of the recourses as required? Thanks, Jay. -----Original Message----- From: pgsql-performance-owner@xxxxxxxxxxxxxx [mailto:pgsql-performance-owner@xxxxxxxxxxxxxx] On Behalf Of Scott Marlowe Sent: Tuesday, February 14, 2006 8:05 AM To: Jay Greenfield Cc: pgsql-performance@xxxxxxxxxxxxxx Subject: Re: [PERFORM] Postgres slower than MS ACCESS 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. ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
