| From: | Manuel Rigger <rigger(dot)manuel(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: ERROR: found unexpected null value in index |
| Date: | 2019-07-12 23:18:53 |
| Message-ID: | CA+u7OA4suVX48cXTT+iRBE9x5Epe7=qzbu4TLH-X-eQPcPt3_w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Thanks for fixing this!
Best,
Manuel
On Fri, Jul 12, 2019 at 10:28 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> I wrote:
> > Peter Geoghegan <pg(at)bowt(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-07-13 05:49:54 | Re: BUG #15905: FATAL: the database system is starting up |
| Previous Message | Tom Lane | 2019-07-12 20:33:10 | 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 |