Re: Thick indexes - a look at count(1) query

From: "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com>
To: "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "Gokulakannan Somasundaram" <gokul007(at)gmail(dot)com>
Cc: Decibel! <decibel(at)decibel(dot)org>, "pgsql-hackers list" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Thick indexes - a look at count(1) query
Date: 2008-01-23 17:35:53
Message-ID: 1d4e0c10801230935l7d56e06bq9948ade32ad14a07@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jan 23, 2008 5:48 PM, Martijn van Oosterhout <kleptog(at)svana(dot)org> wrote:
> On Wed, Jan 23, 2008 at 10:02:14PM +0530, Gokulakannan Somasundaram wrote:
> > As you said, 'gettimeofday' is occupying 40% of the execution time. But
> > without explain analyze(with just executor stats), i am not getting the time
> > duration at all. Is there any other way, i can get the timings without this
> > overhead?
>
> \timing iirc.

Yep, it's \timing.

You can also use log_min_duration_statement and pgFouine to have
average stats on a longer run.

--
Guillaume

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Gokulakannan Somasundaram 2008-01-23 19:45:02 Re: [HACKERS] Including Snapshot Info with Indexes
Previous Message Jonah H. Harris 2008-01-23 17:19:38 Re: [HACKERS] Including Snapshot Info with Indexes