Re: BUG #17512: Process running query fails with SIGSEV - nodeMemoize.c:349

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Aleš Zelený <zeleny(dot)ales(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17512: Process running query fails with SIGSEV - nodeMemoize.c:349
Date: 2022-06-08 00:41:17
Message-ID: CAApHDvp5y2xOpms8XAJU0cbpw00Ds1FYg7jW7v0Pp+XANdLVNQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, 8 Jun 2022 at 11:43, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> > My thoughts are that we likely should make this code more robust,
> > despite the bug not being related to a broken data type. I'm only just
> > over the fence on that one though. Any thoughts?
>
> Strong +1, but please s/unable to/could not/, per message style
> guidelines.

Thanks for the review. I've now pushed the adjusted patch.

David

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Fabien COELHO 2022-06-08 10:16:22 Re: psql 15beta1 does not print notices on the console until transaction completes
Previous Message Tom Lane 2022-06-07 23:43:01 Re: BUG #17512: Process running query fails with SIGSEV - nodeMemoize.c:349