|From:||Andrey Borodin <x4mmm(at)yandex-team(dot)ru>|
|To:||Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>|
|Cc:||Костя Кузнецов <chapaev28(at)ya(dot)ru>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: New gist vacuum.|
|Views:||Raw Message | Whole Thread | Download mbox|
> 31 янв. 2016 г., в 17:18, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> написал(а):
> Костя Кузнецов wrote:
>> <div>Thank you, Jeff.</div><div>I reworking patch now. All // warning will be deleted.</div><div>About memory consumption new version will control size of stack and will operate with map of little size because i want delete old style vacuum(now if maintenance_work_mem less than needed to build info map we use old-style vacuum with logical order).</div>
> You never got around to submitting the updated version of this patch,
> and it's been a long time now, so I'm marking it as returned with
> feedback for now. Please do submit a new version once you have it,
> since this seems to be very useful.
I've rebased patch (see attachment), it seems to work. It still requires a bit of styling, docs and tests, at least.
Also, I thinks that hash table is not very good option if we have all pages there: we should either use array or do not fill table for every page.
If author and community do not object, I want to continue work on Konstantin's patch.
Best regards, Andrey Borodin.
|Next Message||Tom Lane||2017-11-12 19:00:42||Re: Fix number skipping in to_number|
|Previous Message||Andrea Adami||2017-11-12 18:17:25||Row Level Security Bug ?|