| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SimpleLruTruncate() mutual exclusion |
| Date: | 2019-11-04 02:26:35 |
| Message-ID: | CA+hUKGKoZAZ2CpvYa-ZQ8-Ee4BW9NGcwQv-KRZViDsMGObWtew@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 1, 2019 at 6:51 PM Noah Misch <noah(at)leadboat(dot)com> wrote:
> vac_truncate_clog() instance 1 starts, considers segment ABCD eligible to unlink
> vac_truncate_clog() instance 2 starts, considers segment ABCD eligible to unlink
> vac_truncate_clog() instance 1 unlinks segment ABCD
> vac_truncate_clog() instance 1 calls SetTransactionIdLimit()
> vac_truncate_clog() instance 1 finishes
> some backend calls SimpleLruZeroPage(), creating segment ABCD
> vac_truncate_clog() instance 2 unlinks segment ABCD
>
> Serializing vac_truncate_clog() fixes that.
I've wondered before (in a -bugs thread[1] about unexplained pg_serial
wraparound warnings) if we could map 64 bit xids to wide SLRU file
names that never wrap around and make this class of problem go away.
Unfortunately multixacts would need 64 bit support too...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2019-11-04 02:40:43 | Re: [HACKERS] Block level parallel vacuum |
| Previous Message | Thomas Munro | 2019-11-04 01:28:36 | Re: fe-utils - share query cancellation code |