Re: planner chooses unoptimal plan on joins with complex key

From: "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com>
To: "Dmitry Potapov" <fortune(dot)fish(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: planner chooses unoptimal plan on joins with complex key
Date: 2008-01-23 13:58:52
Message-ID: 1d4e0c10801230558i1e56a9dcgaa9e6c2fac6d0448@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Dmitry,

On Jan 23, 2008 2:48 PM, Dmitry Potapov <fortune(dot)fish(at)gmail(dot)com> wrote:
> EXPLAIN ANALYZE SELECT * FROM t1t2_view ORDER BY time_stamp ASC LIMIT 100:
>
> Limit (cost=13403340.40..13403340.40 rows=1 width=152)

It doesn't look like an EXPLAIN ANALYZE output. Can you provide a real
one (you should have a second set of numbers with EXPLAIN ANALYZE)?

Thanks,

--
Guillaume

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Bill Moran 2008-01-23 14:59:08 Re: Making the most of memory?
Previous Message Dmitry Potapov 2008-01-23 13:48:16 planner chooses unoptimal plan on joins with complex key