From: | Marti Raudsepp <marti(at)juffo(dot)org> |
---|---|
To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
Cc: | Andreas Karlsson <andreas(at)proxel(dot)se>, David Rowley <dgrowleyml(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)2ndquadrant(dot)com>, Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Subject: | Re: PoC: Partial sort |
Date: | 2014-01-14 19:39:42 |
Message-ID: | CABRT9RDd-P2RLRdHsMq8rCOB46k4a5O+bGz_up2bRGeeH4R6oQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jan 14, 2014 at 9:28 PM, Alexander Korotkov <aekorotkov(at)gmail(dot)com>wrote:
> On Tue, Jan 14, 2014 at 11:16 PM, Marti Raudsepp <marti(at)juffo(dot)org> wrote:
>
>> Oh, this actually highlights a performance regression with the partial
>> sort patch.
>>
>
> Interesting. Could you share the dataset?
>
It occurs with many datasets if work_mem is sufficiently low (10MB in my
case). Here's a quicker way to reproduce a similar issue:
create table foo as select i, i as j from generate_series(1,10000000) i;
create index on foo(i);
explain analyze select * from foo a join foo b using (i, j);
The real data is from the "release" table from MusicBrainz database dump:
https://musicbrainz.org/doc/MusicBrainz_Database/Download . It's nontrivial
to set up though, so if you still need the real data, I can upload a pgdump
for you.
Regards,
Marti
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2014-01-14 19:40:38 | Re: [Lsf-pc] Linux kernel impact on PostgreSQL performance |
Previous Message | Robert Haas | 2014-01-14 19:35:18 | Re: Comment typo in src/include/access/gin_private.h |