From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: subselect requires offset 0 for good performance. |
Date: | 2013-08-01 21:15:09 |
Message-ID: | CAHyXU0yngt7C8HGNpujbeNA356=BLXNVAtpEjC7cSjdTt6QEew@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, Aug 1, 2013 at 2:40 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> Howdy. I seem to have inherited this problem:
>
> http://www.postgresql.org/message-id/EF524E81-B815-4122-A337-7E50BCED514E@silentmedia.com
>
> Basically a subselect with no offset is resulting in really poor
> performance with 120s queries but adding an offset 0 to the inner sub
> select results in 0.5s query times, and I get the same output.
>
> The original answer Robert Haas asks for a self contained test case.
>
> I am running 8.4.15 and can try 8.4.17 if some patch has been applied
> to it to address this issue. I just want to know should I
>
> A: upgrade to 8.4.17
> or
> B: create a self contained test case.
IMNSHO, I would pursue both (unless A solves your problem in which
case B is moot).
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Sergey Burladyan | 2013-08-01 21:50:23 | Re: Looks like merge join planning time is too big, 55 seconds |
Previous Message | Jeff Janes | 2013-08-01 19:51:04 | Re: Looks like merge join planning time is too big, 55 seconds |