| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: New IndexAM API controlling index vacuum strategies |
| Date: | 2021-01-20 01:14:25 |
| Message-ID: | CAH2-WzmiOSY8EwRuYwcdWJFYV3Mr-SmR3rx7qgvXAF_16_LpnA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 19, 2021 at 4:45 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> BTW, I think that increasing MaxHeapTuplesPerPage will make it
> necessary to consider tidbitmap.c. Comments at the top of that file
> say that it is assumed that MaxHeapTuplesPerPage is about 256. So
> there is a risk of introducing performance regressions affecting
> bitmap scans here.
More concretely, WORDS_PER_PAGE increases from 5 on the master branch
to 16 with the latest version of the patch series on most platforms
(while WORDS_PER_CHUNK is 4 with or without the patches).
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hou, Zhijie | 2021-01-20 01:16:38 | RE: Add Nullif case for eval_const_expressions_mutator |
| Previous Message | Peter Geoghegan | 2021-01-20 00:45:22 | Re: New IndexAM API controlling index vacuum strategies |