| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Manuel Rigger <rigger(dot)manuel(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: ERROR: found unexpected null value in index |
| Date: | 2019-07-10 03:06:50 |
| Message-ID: | CAH2-WzkNv-HyAGvkkq4ymv1fJTr+jrLCQqiXaopXSE3DUo_ncA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Jul 9, 2019 at 7:47 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-07-10 04:51:47 | Re: BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot |
| Previous Message | Tom Lane | 2019-07-10 02:47:01 | Re: ERROR: found unexpected null value in index |