Nickolay <nitro(at)zhukcity(dot)ru> writes:
> BUT it seems that rarely this transaction is being delayed to apply and
> log entry is being inserted in wrong order:
> ID timestamp
> 1 2009-08-08 00:00:00.111
> 2 2009-08-08 00:00:30.311
> 3 2009-08-08 00:00:00.211
> Yep, that's right - sometimes for 30 seconds or even more.
You haven't provided enough information to let anyone guess at the
problem. Have you checked to see if one of the processes is blocking
on a lock, or perhaps there's a sudden spike in system load, or what?
Watching pg_stat_activity, pg_locks, and/or "vmstat 1" output during
one of these events might help narrow down what's happening.
regards, tom lane
In response to
pgsql-performance by date
|Next:||From: Tom Lane||Date: 2009-08-12 21:57:34|
|Subject: Re: Why is vacuum_freeze_min_age 100m? |
|Previous:||From: Pierre Frédéric Caillaud||Date: 2009-08-12 21:34:19|
|Subject: Re: transaction delays to apply|