Skip site navigation (1) Skip section navigation (2)

Re: concurrency performance degradation

From: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
To: Sheer El-Showk <sheer(at)saraf(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: concurrency performance degradation
Date: 2001-10-29 14:28:50
Message-ID: 3BDD67A2.6D644EE6@fourpalms.org (view raw or flat)
Thread:
Lists: pgsql-general
...
> The reason I mention foreign keys above is that I imagine that foreign
> keys might complicate locking issues and I use them a _lot_.  I also
> noticed that the database slows down significantly as it gets populated.
> When I get to about 8000 transactions (~8000 records in my primary table)
> it is much slower, and by 19k it takes up to 5-15 seconds to do an insert.
> A "vacuum analyze" didn't help here.

But appropriate indices should help. Updates which require sequential
scans are expensive as tables get bigger, and the scaling problem you
describe is the usual symptom of missing indices.

Use "explain" and examine your queries to tune the performance.

                     - Thomas

In response to

Responses

pgsql-general by date

Next:From: Denis GasparinDate: 2001-10-29 14:36:00
Subject: Re: [ODBC] Writing BLOBS to pgsql via ODBC using VB - Mini
Previous:From: Tatsuo IshiiDate: 2001-10-29 12:26:19
Subject: Re: resend: Chinese sort order problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group