| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Melanie Plageman <melanieplageman(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Noah Misch <noah(at)leadboat(dot)com> |
| Subject: | Re: Vacuum ERRORs out considering freezing dead tuples from before OldestXmin |
| Date: | 2024-06-25 18:35:00 |
| Message-ID: | CA+TgmoYr5wY1B7kyYFJRcG_xMUqBqvfRdVhy5=D80r+VgOb7eA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 25, 2024 at 1:10 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> That said, obviously there will be plenty setups where this won't cause an
> issue. I don't really have a handle on how often it'd be a problem.
Fair enough. Even if it's not super-common, it doesn't seem like a
great idea to regress such scenarios in the back-branches.
Is there any way that we could instead tweak things so that we adjust
the visibility test object itself? Like can have a GlobalVisTest API
where we can supply the OldestXmin from the VacuumCutoffs and have it
... do something useful with that?
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2024-06-25 19:26:46 | Re: improve predefined roles documentation |
| Previous Message | David E. Wheeler | 2024-06-25 17:55:17 | Re: Proposal: Document ABI Compatibility |