From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Hans-Jürgen Schönig <postgres(at)cybertec(dot)at> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Boszormenyi Zoltan <zb(at)cybertec(dot)at>, pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: plan time of MASSIVE partitioning ... |
Date: | 2010-09-08 15:33:26 |
Message-ID: | AANLkTikE8GAGmSGvKdd=BL2dRX9frnT8uzoXscu9zpUD@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2010/9/8 Hans-Jürgen Schönig <postgres(at)cybertec(dot)at>:
> On Sep 8, 2010, at 4:57 PM, Stephen Frost wrote:
>
>> * Robert Haas (robertmhaas(at)gmail(dot)com) wrote:
>>> Neat. Have you checked what effect this has on memory consumption?
>>>
>>> Also, don't forget to add it to
>>> https://commitfest.postgresql.org/action/commitfest_view/open
>>
>> Would be good to have the patch updated to be against HEAD before
>> posting to the commitfest.
>
>
> we will definitely provide something which is for HEAD.
> but, it seems the problem we are looking is not sufficiently fixed yet.
> in our case we shaved off some 18% of planning time or so - looking at the other top 2 functions i got the feeling that more can be done to reduce this. i guess we have to attack this as well.
Just remember that four small patches (say) are apt to get committed
faster than one big one.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2010-09-08 15:37:30 | Re: plan time of MASSIVE partitioning ... |
Previous Message | Stephen Frost | 2010-09-08 15:26:55 | Re: plan time of MASSIVE partitioning ... |