| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
| Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: RFC: Key normalization for nbtree |
| Date: | 2017-07-10 20:23:46 |
| Message-ID: | 20170710202346.dorxanjjiuwh2gmy@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Claudio Freire wrote:
> A missing optimization is that having tid unification allows VACUUM to
> implement a different strategy when it needs to clean up only a tiny
> fraction of the index. It can do the lookup by key-tid instead of
> scanning the whole index, which can be a win if the index is large and
> the number of index pointers to kill is small.
Doing index cleanup by using keys instead of scanning the whole index
would be a *huge* win for many use cases. I don't think that work needs
to be related to either of these patches.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2017-07-10 20:36:29 | Re: RFC: Key normalization for nbtree |
| Previous Message | Peter J. Holzer | 2017-07-10 20:17:15 | Re: [HACKERS] Postgres process invoking exit resulting in sh-QUIT core |