| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Testing autovacuum wraparound (including failsafe) |
| Date: | 2021-04-24 02:56:38 |
| Message-ID: | CAH2-Wz=KDNbv-8ZhN4q1_8V70P8MqeJjfNHgh0GWgKEjf_f+4Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Apr 23, 2021 at 7:53 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> I mainly suggested it because to me the current seems hard to
> understand. I do think it'd be better to check more often. But checking
> depending on the amount of dead tuples at the right time doesn't strike
> me as a good idea - a lot of anti-wraparound vacuums will mainly be
> freezing tuples, rather than removing a lot of dead rows. Which makes it
> hard to understand when the failsafe kicks in.
I'm convinced -- decoupling the logic from the one-pass-not-two pass
case seems likely to be simpler and more useful. For both the one pass
and two pass/has indexes case.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2021-04-24 02:57:35 | Re: [PATCH] force_parallel_mode and GUC categories |
| Previous Message | Amit Kapila | 2021-04-24 02:53:25 | Re: [bug?] Missed parallel safety checks, and wrong parallel safety |