Re: Weird index or sort behaviour

From: Matthew Wakeling <matthew(at)flymine(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Greg Stark <gsstark(at)mit(dot)edu>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Weird index or sort behaviour
Date: 2009-11-18 11:39:03
Message-ID: alpine.DEB.2.00.0911181136450.684@aragorn.flymine.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Sat, 14 Nov 2009, Tom Lane wrote:
> Matthew Wakeling <matthew(at)flymine(dot)org> writes:
>> [ discussion about applying materialize to a mergejoin's inner indexscan ]
>
> I have finally gotten round to doing something about this, and applied
> the attached patch to CVS HEAD. Could you test it on your problem case
> to see what happens? If it's not convenient to load your data into
> 8.5devel, I believe the patch would work all right in 8.4.x. (A quick
> check shows that it applies except for one deletion hunk that has a
> conflict due to a comment change; you could easily do that deletion
> manually.)

Um, cool. I'm going to have to look back at the archives to even work out
what query I was complaining about though. May take a little while to
test, but I'll get back to you. Thanks,

Matthew

--
The only secure computer is one that's unplugged, locked in a safe,
and buried 20 feet under the ground in a secret location...and i'm not
even too sure about that one. --Dennis Huges, FBI

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Waldomiro 2009-11-18 16:22:30 Too much blocks read
Previous Message Grzegorz Jaśkiewicz 2009-11-18 08:17:44 Re: Performance regression 8.3.8 -> 8.4.1 with NOT EXISTS