Re: [HACKERS] Vacuum: allow usage of more than 1GB of work mem
| От | Claudio Freire |
|---|---|
| Тема | Re: [HACKERS] Vacuum: allow usage of more than 1GB of work mem |
| Дата | |
| Msg-id | CAGTBQpbe36CUJLvmiVPbZyEEY=7SMkQZr=11mOV9J834bLNqRA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] Vacuum: allow usage of more than 1GB of work mem (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>) |
| Ответы |
Re: [HACKERS] Vacuum: allow usage of more than 1GB of work mem
|
| Список | pgsql-hackers |
On Tue, Feb 6, 2018 at 4:35 AM, Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp> wrote: >> It's starting to look like a timing effect indeed. > > It seems to be truncation skip, maybe caused by concurrent > autovacuum. Good point, I'll also disable autovacuum on vactst. > See lazy_truncate_heap() for details. Updates of > pg_stat_*_tables can be delayed so looking it also can fail. Even > though I haven't looked the patch closer, the "SELECT > pg_relation_size()" doesn't seem to give something meaningful > anyway. Maybe then "explain (analyze, buffers, costs off, timing off, summary off) select * from vactst" then. The point is to check that the relation's heap has 0 pages.
В списке pgsql-hackers по дате отправления: