From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: cutting down the TODO list thread |
Date: | 2023-05-16 08:50:45 |
Message-ID: | 20230516085045.tugzp5w6kwenfv3k@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2023-May-13, John Naylor wrote:
> --------------------
> 2. Propose to move to the "Not Wanted list":
> Consider having single-page pruning update the visibility map
> -> Comment from Heikki in the thread:
> "I think I was worried about the possible performance impact of having to
> clear the bit in visibility map again. If you're frequently updating a
> tuple so that HOT and page pruning is helping you, setting the bit in
> visibility map seems counter-productive; it's going to be cleared soon
> again by another UPDATE. That's just a hunch, though. Maybe the overhead
> is negligible."
Hmm, I agree with removing the entry from the TODO list, but why is this
something we Do Not Want? If somebody shows up and do some analysis
that in a certain workload it is beneficial to do this, then I don't
think we should turn them down.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Gustafsson | 2023-05-16 09:17:17 | Re: pgsql: Clean up role created in new subscription test. |
Previous Message | Daniel Gustafsson | 2023-05-16 08:19:26 | Re: Using make_ctags leaves tags files in git |