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

From Peter Geoghegan
Subject Re: ERROR: found unexpected null value in index
Date
Msg-id CAH2-WzkNv-HyAGvkkq4ymv1fJTr+jrLCQqiXaopXSE3DUo_ncA@mail.gmail.com
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  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Tue, Jul 9, 2019 at 7:47 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > Back when get_actual_variable_range() used a dirty snapshot, it would
> > have not seen any NULL value with this test case, because the root of
> > the HOT chain would be considered recently dead.
>
> Hm.  So maybe we need to teach it to ignore tuples that are not the tips
> of their HOT chains?

An approach like that was the first thing that I thought of, but I'll
have to study the problem some more before coming up with a firm
opinion.


-- 
Peter Geoghegan



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: ERROR: found unexpected null value in index
Next
From: Michael Paquier
Date:
Subject: Re: BUG #15888: Bogus "idle in transaction" state for logicaldecoding client after creating a slot