Re: subselect requires offset 0 for good performance. - Mailing list pgsql-performance

From Merlin Moncure
Subject Re: subselect requires offset 0 for good performance.
Date
Msg-id CAHyXU0yngt7C8HGNpujbeNA356=BLXNVAtpEjC7cSjdTt6QEew@mail.gmail.com
Whole thread Raw
In response to subselect requires offset 0 for good performance.  (Scott Marlowe <scott.marlowe@gmail.com>)
List pgsql-performance
On Thu, Aug 1, 2013 at 2:40 PM, Scott Marlowe <scott.marlowe@gmail.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


pgsql-performance by date:

Previous
From: Jeff Janes
Date:
Subject: Re: Looks like merge join planning time is too big, 55 seconds
Next
From: Sergey Burladyan
Date:
Subject: Re: Looks like merge join planning time is too big, 55 seconds