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

Help with duration of statement: EXECUTE <unnamed> [PREPARE: COMMIT]

From: Eric Comeau <ecomeau(at)signiant(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Help with duration of statement: EXECUTE <unnamed> [PREPARE: COMMIT]
Date: 2010-10-16 12:32:11
Message-ID: i9c60b$ifv$1@news.hub.org (view raw or flat)
Thread:
Lists: pgsql-performance
We currently have

   log_min_duration_statement = 5000

and are seeing statements like the following logged

2010-10-16 05:55:52 EDT [6334]: [1-1] LOG:  duration: 5572.517 ms 
statement: EXECUTE <unnamed>  [PREPARE:  COMMIT]
2010-10-16 06:06:24 EDT [26856]: [1-1] LOG:  duration: 5617.866 ms 
statement: EXECUTE <unnamed>  [PREPARE:  COMMIT]
2010-10-16 06:06:24 EDT [20740]: [13-1] LOG:  duration: 5210.190 ms 
statement: EXECUTE <unnamed>  [PREPARE:  COMMIT]
2010-10-16 08:24:06 EDT [8743]: [1-1] LOG:  duration: 6487.346 ms 
statement: EXECUTE <unnamed>  [PREPARE:  COMMIT]

Questions;

1) What do these statements mean?
2) How do I dig deeper to determine why they are taking longer than 5 secs.

Version Info -->

select version();
                                                   version 

------------------------------------------------------------------------------------------------------------
  PostgreSQL 8.1.17 on x86_64-unknown-linux-gnu, compiled by GCC gcc 
(GCC) 4.1.1 20070105 (Red Hat 4.1.1-52)

Responses

pgsql-performance by date

Next:From: Alvaro HerreraDate: 2010-10-16 15:29:39
Subject: Re: No hash join across partitioned tables?
Previous:From: Samuel GendlerDate: 2010-10-16 05:35:46
Subject: Re: No hash join across partitioned tables?

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