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

Re: transaction delays to apply

From: Pierre Frédéric Caillaud <lists(at)peufeu(dot)com>
To: Nickolay <nitro(at)zhukcity(dot)ru>, pgsql-performance(at)postgresql(dot)org
Subject: Re: transaction delays to apply
Date: 2009-08-12 21:34:19
Message-ID: op.uykjjhujcke6l8@soyouz (view raw or flat)
Thread:
Lists: pgsql-performance
> Does anybody know any way to solve this? I did monitor the system  
> running at full load (~20 messages per second) - postmaster's processes  
> didn't eat more than 10-20% of CPU and memory. Neither did any of my  
> application's processes.

now() like current_timestamp is the time of transaction start. If your  
client BEGINs, then idles for 30 seconds, then INSERTs, the timestamp in  
the insert will be from 30 second ago. Try statement_timestamp() or  
clock_timestamp().

In response to

pgsql-performance by date

Next:From: Tom LaneDate: 2009-08-12 21:37:39
Subject: Re: transaction delays to apply
Previous:From: Kevin GrittnerDate: 2009-08-12 21:33:44
Subject: Re: Why is vacuum_freeze_min_age 100m?

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