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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, cameron(dot)ezell(at)clearcapital(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Subject: Re: BUG #16369: Segmentation Faults and Data Corruption with Generated Columns
Date: 2020-04-18 09:28:56
Message-ID: 20200418092856.GE350229@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, Apr 18, 2020 at 02:13:17PM +1200, David Rowley wrote:
> On Thu, 16 Apr 2020 at 17:30, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> > Shouldn't you have more regression test cases here? I guess one for
> > the non-NULL case, and one for the NULL case?
>
> Yeah. I've just pushed a fix that included a fairly simple regression test.

Thanks for the commit, David! I was wondering if it would have been
better to add a "\pset null", but that's a nit and the result looks
fine anyway.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2020-04-18 10:04:05 BUG #16377: select stuck when use order by and limit 1 if order-by-field has one index and result has no records
Previous Message Michael Paquier 2020-04-18 09:26:11 Re: [BUG] non archived WAL removed during production crash recovery