Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: ERROR: found unexpected null value in index
Date
Msg-id 5671.1562963292@sss.pgh.pa.us
Whole thread Raw
In response to Re: ERROR: found unexpected null value in index  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: ERROR: found unexpected null value in index  (Manuel Rigger <rigger.manuel@gmail.com>)
List pgsql-bugs
Tree view 
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: Rashid Abzalov
Date:
Subject: Re: The statement is re-executed (performed twice) on commit if it isdeclared as "cursor with hold" and the cursor is not closed yet
Next
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