Re: [PERFORM] timing != log duration

2012-03-21 Thread Albe Laurenz
Rafael Martinez wrote: > I am wondering why the time reported by \timing in psql is not the same > as the time reported by duration in the log file when log_duration or > log_min_duration_statement are on?. I can not find any information about > this in the documentation. \timing measures the time

Re: [PERFORM] set autovacuum=off

2012-03-21 Thread Robert Haas
On Thu, Feb 23, 2012 at 3:28 PM, Alessandro Gagliardi wrote: > I'm unable to make sense of pg_locks. The vast majority are > locktype='transactionid', mode='ExclusiveLock', granted=t. There are some > 'relation' locks with mode='RowExclusiveLock' and fewer with > 'AccessShareLock'. I have no idea

Re: [PERFORM] timing != log duration

2012-03-21 Thread Tom Lane
Rafael Martinez writes: > I am wondering why the time reported by \timing in psql is not the same > as the time reported by duration in the log file when log_duration or > log_min_duration_statement are on? Network transmission delays, perhaps? psql reports the elapsed time seen at the client, w

Re: [PERFORM] DBD-Pg prepared statement versus plain execution

2012-03-21 Thread Andy Colson
On 3/21/2012 6:21 AM, Rafael Martinez wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello We are having some performance problems with an application that uses prepared statement heavily. We have found out that it creates-executes-destroys a prepared statement *per* statement it sends t

Re: [PERFORM] DBD-Pg prepared statement versus plain execution

2012-03-21 Thread k...@rice.edu
Hi Rafael, Try disabling the prepare statement processing in DBD::Pg and try the timing runs again. Regards, Ken On Wed, Mar 21, 2012 at 12:21:23PM +0100, Rafael Martinez wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hello > > We are having some performance problems with an appl

Re: [PERFORM] timing != log duration

2012-03-21 Thread Marti Raudsepp
On Wed, Mar 21, 2012 at 13:42, Rafael Martinez wrote: > I am wondering why the time reported by \timing in psql is not the same > as the time reported by duration in the log file when log_duration or > log_min_duration_statement are on? psql's \timing measures time on the client -- which includes

[PERFORM] timing != log duration

2012-03-21 Thread Rafael Martinez
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello I am wondering why the time reported by \timing in psql is not the same as the time reported by duration in the log file when log_duration or log_min_duration_statement are on?. I can not find any information about this in the documentation. e.

[PERFORM] DBD-Pg prepared statement versus plain execution

2012-03-21 Thread Rafael Martinez
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello We are having some performance problems with an application that uses prepared statement heavily. We have found out that it creates-executes-destroys a prepared statement *per* statement it sends to the database (pg-9.1) via DBD-Pg. A normal l