Re: Queries 15 times slower on 8.1 beta 2 than on 8.0

From: "Jean-Pierre Pelletier" <pelletier_32(at)sympatico(dot)ca>
To: <josh(at)agliodbs(dot)com>, <pgsql-performance(at)postgresql(dot)org>
Cc: "John Arbash Meinel" <john(at)arbash-meinel(dot)com>
Subject: Re: Queries 15 times slower on 8.1 beta 2 than on 8.0
Date: 2005-09-23 01:41:37
Message-ID: BAYC1-PASMTP044401579071F97B30C53F95960@CEZ.ICE
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Explain analyze on my 8.0.1 installation does report the time for
slower queries but for this small query it reports 0.000 ms

----- Original Message -----
From: "Josh Berkus" <josh(at)agliodbs(dot)com>
To: <pgsql-performance(at)postgresql(dot)org>
Cc: "Jean-Pierre Pelletier" <pelletier_32(at)sympatico(dot)ca>; "John Arbash
Meinel" <john(at)arbash-meinel(dot)com>
Sent: Thursday, September 22, 2005 6:19 PM
Subject: Re: [PERFORM] Queries 15 times slower on 8.1 beta 2 than on 8.0

> Jean-Pierre,
>
> First off, you're on Windows?
>
>> " -> Seq Scan on price p (cost=0.00..11317.75 rows=581475 width=4)
>> (actual time=0.004..1143.720 rows=581475 loops=1)"
>
> Well, this is your pain point. Can we see the index scan plan on 8.1?
> Given that it's *expecting* only one row, I can't understand why it's
> using a seq scan ...
>
>> "Nested Loop Left Join (cost=0.00..11.02 rows=1 width=0) (actual
>> time=0.000..0.000 rows=1 loops=1)"
>> " -> Nested Loop Left Join (cost=0.00..5.48 rows=1 width=4) (actual
>> time=0.000..0.000 rows=1 loops=1)"
>> "Total runtime: 0.000 ms"
>
> Feh, this looks like the "windows does not report times" bug, which makes
> it hard to compare ...
>
> --
> --Josh
>
> Josh Berkus
> Aglio Database Solutions
> San Francisco
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Josh Berkus 2005-09-23 02:49:18 Re: FW: Deadlock Issue with PostgreSQL
Previous Message Anu Kucharlapati 2005-09-23 00:21:33 FW: Deadlock Issue with PostgreSQL