From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: do only critical work during single-user vacuum? |
Date: | 2022-02-15 23:17:25 |
Message-ID: | CAH2-WznMo_aEQJJrD1G70RbbWRB9C3gFf3Am6emYrWSTh6wu=w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Feb 15, 2022 at 9:28 AM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> On Mon, Feb 14, 2022 at 10:04 PM John Naylor
> <john(dot)naylor(at)enterprisedb(dot)com> wrote:
> > Well, the point of inventing this new vacuum mode was because I
> > thought that upon reaching xidStopLimit, we couldn't issue commands,
> > period, under the postmaster. If it was easier to get a test instance
> > to xidStopLimit, I certainly would have discovered this sooner.
>
> I did notice from my own testing of the failsafe (by artificially
> inducing wraparound failure using an XID burning C function) that
> autovacuum seemed to totally correct the problem, even when the system
> had already crossed xidStopLimit - it came back on its own. I wasn't
> completely sure of how robust this effect was, though.
It seemed worth noting this in comments above
should_attempt_truncation(). Pushed a commit to do that just now.
Thanks
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2022-02-15 23:33:37 | Re: Column Filtering in Logical Replication |
Previous Message | Nathan Bossart | 2022-02-15 23:11:23 | Re: Avoid erroring out when unable to remove or parse logical rewrite files to save checkpoint work |