Re: ERROR: found unexpected null value in index - Mailing list pgsql-bugs

From Manuel Rigger
Subject Re: ERROR: found unexpected null value in index
Date
Msg-id CA+u7OA4suVX48cXTT+iRBE9x5Epe7=qzbu4TLH-X-eQPcPt3_w@mail.gmail.com
Whole thread Raw
In response to Re: ERROR: found unexpected null value in index  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Thanks for fixing this!

Best,
Manuel

On Fri, Jul 12, 2019 at 10:28 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> I wrote:
> > Peter Geoghegan <pg@bowt.ie> writes:
> >> Interesting approach. I certainly prefer it to the alternative
> >> approach of framing the problem as a visibility concern.
>
> > Yes, I certainly like this better than my previous attempt.
>
> Re-reading the patch, I realized that it wasn't using the ExecutorState
> infrastructure anymore, except for a short-lived memory context.  So we
> can get an additional small savings by dropping the executor dependency
> and just making a temp context for ourselves.
>
> Pushed with that improvement.
>
>                         regards, tom lane



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: The statement is re-executed (performed twice) on commit if it is declared as "cursor with hold" and the cursor is not closed yet
Next
From: Michael Paquier
Date:
Subject: Re: BUG #15905: FATAL: the database system is starting up