From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pg15b1: FailedAssertion("val > base", File: "...src/include/utils/relptr.h", Line: 67, PID: 30485) |
Date: | 2022-06-22 04:24:06 |
Message-ID: | CA+hUKGJ9pXo0v8wO0cUoNvcSK9R4z+puXPmk+TUcJHQ9Yjw6Cw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jun 22, 2022 at 2:54 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> John Naylor <john(dot)naylor(at)enterprisedb(dot)com> writes:
> > On Wed, Jun 1, 2022 at 2:57 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> >> ... So we can fix this by:
> >> 1. Using a relative pointer value other than 0 to represent a null
> >> pointer. Andres suggested (Size) -1.
> >> 2. Not storing the free page manager for the DSM in the main shared
> >> memory segment at byte offset 0.
For the record, the third idea proposed was to use 1 for the first
byte, so that 0 is reserved for NULL and works with memset(0). Here's
an attempt at that.
Attachment | Content-Type | Size |
---|---|---|
0001-Fix-relptr-s-encoding-of-NULL.patch | text/x-patch | 4.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2022-06-22 04:28:14 | Re: Skipping logical replication transactions on subscriber side |
Previous Message | Amit Kapila | 2022-06-22 04:18:23 | Re: tablesync copy ignores publication actions |