| From: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> |
|---|---|
| To: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Subject: | Re: SKIP LOCKED assert triggered |
| Date: | 2021-12-01 19:38:22 |
| Message-ID: | CANbhV-Ek8nbeyOxGVUgpnj6TFwj8aZDJsQf-8z-FP1Sx3vK6FA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 1 Dec 2021 at 14:33, Bossart, Nathan <bossartn(at)amazon(dot)com> wrote:
>
> On 11/12/21, 8:56 AM, "Simon Riggs" <simon(dot)riggs(at)enterprisedb(dot)com> wrote:
> > The combination of these two statements in a transaction hits an
> > Assert in heapam.c at line 4770 on REL_14_STABLE
>
> I've been unable to reproduce this. Do you have any tips for how to
> do so? Does there need to be some sort of concurrent workload?
That path is only ever taken when there are multiple sessions, and as
I said, pgbench finds this reliably. I guess I didn't say "use -c 2"
--
Simon Riggs http://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bossart, Nathan | 2021-12-01 20:24:25 | O(n) tasks cause lengthy startups and checkpoints |
| Previous Message | Bossart, Nathan | 2021-12-01 19:33:05 | Re: SKIP LOCKED assert triggered |