On Thu, 2007-09-13 at 11:10 -0400, Tom Lane wrote:
> Brad Nicholson <bnichols@ca.afilias.info> writes:
> > On Thu, 2007-09-13 at 10:15 -0400, Brad Nicholson wrote:
> >> I'm having a problem with long running commits appearing in my database
> >> logs. It may be hardware related, as the problem appeared when we moved
> >> the database to a new server connected to a different disk array.
>
> > More on this - we also have long running commits on installations that
> > do have the wal files on a separate partition.
>
> What's your definition of "long running commit" --- seconds? milliseconds?
> Exactly what are you measuring? Can you correlate the problem with what
log_min_duration is set to 150ms
Commits running over that up to 788ms. Here is what we see in the logs
(with obfuscated dbname, username and IP):
2007-09-13 10:01:49.787 CUT [782426] dbname username 1.2.3.171 LOG:
duration: 224.286 ms statement: EXECUTE <unnamed> [PREPARE: commit]
2007-09-13 10:19:16.373 CUT [737404] dbname username 1.2.3.174 LOG:
duration: 372.545 ms statement: EXECUTE <unnamed> [PREPARE: commit]
2007-09-13 10:19:24.437 CUT [1806498] dbname username 11.2.3.171 LOG:
duration: 351.544 ms statement: EXECUTE <unnamed> [PREPARE: commit]
2007-09-13 10:33:11.204 CUT [962598] dbname username 1.2.3.170 LOG:
duration: 504.057 ms statement: EXECUTE <unnamed> [PREPARE: commit]
2007-09-13 10:40:33.735 CUT [1282104] dbname username 1.2.3.174 LOG:
duration: 250.127 ms statement: EXECUTE <unnamed> [PREPARE: commit]
2007-09-13 10:49:54.752 CUT [1188032] dbname username 1.2.3.170 LOG:
duration: 382.781 ms statement: EXECUTE <unnamed> [PREPARE: commit]
2007-09-13 11:30:43.339 CUT [1589464] dbname username 1.2.3.172 LOG:
duration: 408.463 ms statement: EXECUTE <unnamed> [PREPARE: commit]
--
Brad Nicholson 416-673-4106
Database Administrator, Afilias Canada Corp.
