Horton

Re: ERROR: found unexpected null value in index

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Andres Freund <andres@anarazel.de>, Manuel Rigger <rigger.manuel@gmail.com>, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2019-07-12T20:28:12Z
Lists: pgsql-bugs 
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

Commits

  1. Fix get_actual_variable_range() to cope with broken HOT chains.

  2. Improve performance of get_actual_variable_range with recently-dead tuples.