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

Re: Big difference in time returned by EXPLAIN ANALYZE SELECT ... AND SELECT ...

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: Vitalii Tymchyshyn <tivv00(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Big difference in time returned by EXPLAIN ANALYZE SELECT ... AND SELECT ...
Date: 2010-07-26 09:56:57
Message-ID: 4C4D5BE9.6040808@postnewspapers.com.au (view raw or flat)
Thread:
Lists: pgsql-performance
On 26/07/10 17:25, Vitalii Tymchyshyn wrote:
> 26.07.10 12:15, Craig Ringer написав(ла):
>> On 26/07/10 16:35, Piotr Gasidło wrote:
>>   
>>> Hello,
>>>
>>> I've found strange problem in my database (8.4.4, but also 9.0beta3,
>>> default postgresql.conf, shared_buffers raised to 256MB).
>>>
>>> EXPLAIN ANALYZE SELECT ...
>>> Total runtime: 4.782 ms
>>> Time: 25,970 ms

>> Given that, I'm wondering if the difference in this case is planning
>> time. I can't really imagine the query planner taking 20 seconds (!!) to
>> run, though, no matter how horrifyingly complicated the query and table
>> structure were, unless there was something going wrong.
>>    
> Actually it's 20ms, so I suspect your point about planning time is correct.

Oh, a commas-as-fraction-separator locale.

That makes sense. Thanks for the catch.

--
Craig Ringer

In response to

Responses

pgsql-performance by date

Next:From: Piotr GasidłoDate: 2010-07-26 10:04:13
Subject: Re: Big difference in time returned by EXPLAIN ANALYZE SELECT ... AND SELECT ...
Previous:From: Matthew WakelingDate: 2010-07-26 09:47:14
Subject: Re: Testing Sandforce SSD

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