From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "McAlister, Grant" <grant(at)amazon(dot)com>, "Mlodgenski, Jim" <mlodj(at)amazon(dot)com>, "Nasby, Jim" <nasbyj(at)amazon(dot)com>, "Hsu, John" <hsuchen(at)amazon(dot)com> |
Subject: | Re: partial heap only tuples |
Date: | 2021-02-13 16:26:23 |
Message-ID: | 20210213162623.4upmsuzwv2anqoqx@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2021-02-09 18:48:21 +0000, Bossart, Nathan wrote:
> In order to be eligible for cleanup, the final tuple in the
> corresponding PHOT/HOT chain must also be eligible for cleanup, or all
> indexes must have been updated later in the chain before any visible
> tuples.
This sounds like it might be prohibitively painful. Adding effectively
unremovable bloat to remove other bloat is not an uncomplicated
premise. I think you'd really need a way to fully remove this as part of
vacuum for this to be viable.
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2021-02-13 16:32:37 | Re: repeated decoding of prepared transactions |
Previous Message | Joel Jacobson | 2021-02-13 16:10:08 | Re: [HACKERS] GSoC 2017: Foreign Key Arrays |