Hello!
> 31 янв. 2016 г., в 17:18, Alvaro Herrera
> написал(а):
>
> Костя Кузнецов wrote:
>> Thank you, Jeff.I reworking patch now. All // warning will
>> be deleted.About memory consumption new version will control size
>> of stack and will operate with map of little size because i want dele
Костя Кузнецов wrote:
> Thank you, Jeff.I reworking patch now. All // warning will be
> deleted.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 buil
Thank you, Jeff.I reworking patch now. All // warning will be deleted.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 vacuu
On Thu, Sep 10, 2015 at 3:52 PM, Костя Кузнецов wrote:
> Hello. I am student from gsoc programm.
> My project is sequantial access in vacuum of gist.
>
> New vacuum has 2 big step:
> physical order scan pages and cleaning after 1 step.
>
>
> 1 scan - scan all pages and create information map(hashm
On Fri, Sep 11, 2015 at 7:52 AM, Костя Кузнецов wrote:
> old version:
>
> INFO: vacuuming "public.point_tbl"
> INFO: scanned index "gpointind" to remove 11184520 row versions
> DETAIL: CPU 84.70s/72.26u sec elapsed 27007.14 sec.
> [...]
>
> new vacuum is about
> INFO: vacuuming "public.point_tbl"
Hello. I am student from gsoc programm.My project is sequantial access in vacuum of gist. New vacuum has 2 big step:physical order scan pages and cleaning after 1 step. 1 scan - scan all pages and create information map(hashmap) and add information to rescan stack( stack of pages that needed to re
