| From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | Amadeo Gallardo <amadeo(at)ruddr(dot)io>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Postgres 16.1 - Bug: cache entry already complete |
| Date: | 2024-01-03 02:36:20 |
| Message-ID: | CAMbWs4861_VxtXhi82uoG2SZSpMpVV5D84PVQHGiZ6KLFQ6NWQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Jan 3, 2024 at 7:59 AM David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> On Wed, 3 Jan 2024 at 12:49, Amadeo Gallardo <amadeo(at)ruddr(dot)io> wrote:
> > Attached is a sample script that I used to reproduce the error. I had to
> add some specific sample data and force-disable certain planner settings,
> as otherwise the problem did not occur.
> > Additionally, here's a trace of the error:
>
> Thanks for the reproducer. I can recreate this using your script
> after adding an ANALYZE after the INSERTs. Without ndistinct
> statistics, the planner won't risk using Memoize.
It seems that the repro script was not sent to the mailing list. I
cannot see it.
Thanks
Richard
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-01-03 03:05:59 | Re: Postgres 16.1 - Bug: cache entry already complete |
| Previous Message | David Rowley | 2024-01-03 01:47:48 | Re: Postgres 16.1 - Bug: cache entry already complete |