| From: | Bowen Shi <zxwsbg12138(at)gmail(dot)com> |
|---|---|
| To: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, Alexander Lakhin <exclusion(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae |
| Date: | 2024-05-13 03:19:16 |
| Message-ID: | CAM_vCuc3iWc_WdMmAWmixa2i_vNy43rWnSc+7732VRcJUBm+zA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
> Obviously we should actually fix this on back branches, but could we
> at least make the retry loop interruptible in some way so people could
> use pg_cancel/terminate_backend() on a stuck autovacuum worker or
> vacuum process?
If the problem happens in versions <= PG 16, we don't have a good solution
(vacuum process holds the exclusive lock cause checkpoint hangs).
Maybe we can make the retry loop interruptible first. However, since we are
using START_CRIT_SECTION, we cannot simply use CHECK_FOR_INTERRUPTS to
handle it.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | peacefultraveler | 2024-05-13 14:16:05 | ORDER BY two columns gives incorrect result on second column |
| Previous Message | Sandeep Thakkar | 2024-05-13 02:34:02 | Re: Postgresql 16.3 installation error (setup file) on Windows 11 |