timing != log duration - Mailing list pgsql-performance

From Rafael Martinez
Subject timing != log duration
Date
Msg-id 4F69BE88.30905@usit.uio.no
Whole thread Raw
Responses Re: timing != log duration  (Marti Raudsepp <marti@juffo.org>)
Re: timing != log duration  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: timing != log duration  ("Albe Laurenz" <laurenz.albe@wien.gv.at>)
List pgsql-performance
-----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.g.
- -----------------------------------
ver=# SELECT * from version ;
Time: 0.450 ms

2012-03-20 16:10:16 CET 29119 LOG:  duration: 0.313 ms  statement:
SELECT * from version ;
- -----------------------------------

ver=# PREPARE foo AS SELECT * from version ;
PREPARE
Time: 0.188 ms

ver=# EXECUTE foo;
Time: 0.434 ms

ver=# DEALLOCATE foo;
DEALLOCATE
Time: 0.115 ms

2012-03-20 16:12:21 CET 29119 LOG:  duration: 0.127 ms  statement:
PREPARE foo AS SELECT * from version ;
2012-03-20 16:12:37 CET 29119 LOG:  duration: 0.303 ms  statement:
EXECUTE foo;
2012-03-20 16:13:24 CET 29119 LOG:  duration: 0.055 ms  statement:
DEALLOCATE foo;
- -----------------------------------

Thanks in advance
regards,
- --
 Rafael Martinez Guerrero
 Center for Information Technology
 University of Oslo, Norway

 PGP Public Key: http://folk.uio.no/rafael/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9pvoUACgkQBhuKQurGihRf3gCfRMv5dQnNA8f/gjcPMv6OPrGz
qHoAn0PPgN1OYMBDQqJes3kRBxH//Y95
=rsAY
-----END PGP SIGNATURE-----

pgsql-performance by date:

Previous
From: Rafael Martinez
Date:
Subject: DBD-Pg prepared statement versus plain execution
Next
From: Marti Raudsepp
Date:
Subject: Re: timing != log duration