| From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | Евгений Горбанев <gorbanyoves(at)basealt(dot)ru>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Assert failure in base_yyparse |
| Date: | 2025-05-15 08:55:08 |
| Message-ID: | CAMbWs48Yke_OP--d+MVDun2Xt5tT2ReYO0_UvsRZf2eGwk_C5w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 15, 2025 at 1:20 AM Alvaro Herrera <alvherre(at)kurilemu(dot)de> wrote:
> On 2025-May-14, Richard Guo wrote:
> > Attached is a patch that implements this. It also renames the
> > internally used option name and updates the error message.
> LGTM.
Thanks. I've pushed this patch and backpatched it through v15. I
didn't backpatch it to v14 or v13, as those branches don't use boolVal
to retrieve the value of the "is_not_null" option, so the assertion
failure doesn't occur there.
Thanks
Richard
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2025-05-15 09:17:53 | Re: Should we optimize the `ORDER BY random() LIMIT x` case? |
| Previous Message | Masahiro Ikeda | 2025-05-15 08:52:06 | Assertion failure in smgr.c when using pg_prewarm with partitioned tables |