| From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, "tanghy(dot)fnst(at)fujitsu(dot)com" <tanghy(dot)fnst(at)fujitsu(dot)com>, "Amit(dot)Kapila(at)fujitsu(dot)com" <Amit(dot)Kapila(at)fujitsu(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [BUG]"FailedAssertion" reported in lazy_scan_heap() when running logical replication |
| Date: | 2021-05-06 13:38:21 |
| Message-ID: | CAFiTN-tvdtKCKZ2BV72gTePS-fWZUhOzbN-OOCMNUwbfya99FQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 6, 2021 at 6:11 PM Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
> Since we set all_visible_according_to_vm before acquiring the buffer
> lock it's likely to happen that the page gets modified and all-visible
> bit is cleared after setting true to all_visible_according_to_vm. This
> assertion can easily be reproduced by adding a delay before the buffer
> lock and invoking autovacuums frequently:
>
Your analysis seems correct to me that before we acquire the page the
someone can modify it. So this assertion is not correct.
--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vignesh C | 2021-05-06 13:52:31 | Re: Identify missing publications from publisher while create/alter subscription. |
| Previous Message | Amit Kapila | 2021-05-06 13:30:33 | Re: [bug?] Missed parallel safety checks, and wrong parallel safety |