Re: BUG #16369: Segmentation Faults and Data Corruption with Generated Columns

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: cameron(dot)ezell(at)clearcapital(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, peter(dot)eisentraut(at)2ndquadrant(dot)com
Subject: Re: BUG #16369: Segmentation Faults and Data Corruption with Generated Columns
Date: 2020-04-16 00:40:24
Message-ID: CAApHDvqFZZOwCi35xi02G=19df7idzminAhibrHEAz4McEnX=w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, 16 Apr 2020 at 11:52, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> > I'd say the fix should be to just datumCopy() the result of the
> > calculation. i.e the attached.
>
> That looks like it'll fail on a null result.

Thanks. I'll have another go then.

Attachment Content-Type Size
fix_generated_column_crash2.patch application/octet-stream 666 bytes

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Elvis Pranskevichus 2020-04-16 01:17:30 Re: BUG #16368: Incorrect function inlining in the presence of a window function
Previous Message Tom Lane 2020-04-16 00:14:05 Re: BUG #16368: Incorrect function inlining in the presence of a window function