From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Postgres 11 release notes |
Date: | 2018-05-11 19:17:47 |
Message-ID: | CAH2-Wz=gWUAFc-xDxkjBxNGuh2B7LVdEWXGjKDbdeK5P0=H14w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | Postg토토 꽁 머니SQL pgsql-www |
On Fri, May 11, 2018 at 12:04 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> I don't think the table being 'append-only' is necessary? Nor does it
> have to be a manual vacuum. And 'needless index scan' sounds less than
> it is/was, namely a full scan of the index. Perhaps something like:
>
> Allow vacuum to skip doing a full scan of btree indexes after VACUUM,
> if not necessary.
>
> or something like that?
I suggest "Allow vacuuming to avoid full index scans for indexes when
there are no dead tuples found in a table. Where necessary, the
behavior can be adjusted via the new configuration parameter
vacuum_cleanup_index_scale_factor."
Also:
* "Allow indexes to be built in parallel" should specify that it only
works for B-Tree index builds.
* Suggest replacement sort item be phrased as: "Remove the
configuration parameter replacement_sort_tuples. <newline> The
replacement selection sort algorithm is no longer used."
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2018-05-11 19:20:17 | Re: Postgres 11 release notes |
Previous Message | Bruce Momjian | 2018-05-11 19:14:24 | Re: Postgres 11 release notes |
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2018-05-11 19:20:17 | Re: Postgres 11 release notes |
Previous Message | Bruce Momjian | 2018-05-11 19:14:24 | Re: Postgres 11 release notes |