From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Cc: Anjan Dave <adave@vantage.com>
Cc: Rod Taylor <pg@rbt.ca>
Subject: Re: can't handle large number of INSERT/UPDATEs
Date: Tue, 26 Oct 2004 11:27:02 -0700
Message-ID: <200410261127.02656.josh@agliodbs.com> (raw)
In-Reply-To: <4BAFBB6B9CC46F41B2AD7D9F4BBAF7850985DC@vt-pe2550-001.vantage.vantage.com>
References: <4BAFBB6B9CC46F41B2AD7D9F4BBAF7850985DC@vt-pe2550-001.vantage.vantage.com>
Anjan,
> It probably is locking issue. I got a long list of locks held when we ran
> select * from pg_locks during a peak time.
Do the back-loaded tables have FKs on them? This would be a likely cause
of lock contention, and thus serializing inserts/updates to the tables.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
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: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com, adave@vantage.com, pg@rbt.ca
Subject: Re: can't handle large number of INSERT/UPDATEs
In-Reply-To: <200410261127.02656.josh@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox