From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: FailedAssertion("pd_idx == pinfo->nparts", File: "execPartition.c", Line: 1689) |
Date: | 2020-08-04 19:48:49 |
Message-ID: | CA+TgmoZ7tsAhoq9SrcsHUGry6LXgU3EOVHmOZjKrn366ojyRBA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Aug 3, 2020 at 12:11 PM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> (gdb) p *pinfo->relid_map(at)414
> (gdb) p *partdesc->oids(at)415
Whoa, I didn't know about using @ in gdb to print multiple elements. Wild!
Anyway, these two arrays differ in that the latter array has 22653702
inserted at the beginning and 22628862 at the end, and also in that a
0 has been removed. This code can't cope with things getting removed,
so kaboom. I think Amit probably has the right idea about what's going
on here and how to fix it, but I haven't yet had time to study it in
detail.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-08-04 20:31:26 | Re: 13dev failed assert: comparetup_index_btree(): ItemPointer values should never be equal |
Previous Message | Mahendra Singh Thalor | 2020-08-04 19:16:38 | Re: display offset along with block number in vacuum errors |