Re: BUG #16369: Segmentation Faults and Data Corruption with Generated Columns
Terry Schmitt <tschmitt@schmittworks.com>
From: Terry Schmitt <tschmitt@schmittworks.com>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Michael Paquier <michael@paquier.xyz>,
David Rowley <dgrowleyml@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, cameron.ezell@clearcapital.com, pgsql-bugs@lists.postgresql.org
Date: 2020-04-17T17:06:23Z
Lists: pgsql-bugs
I've tried creating a smaller test case, but it's difficult. I haven't > fully understood the reason why it sometimes crashes and sometimes not. > The smallest I could come up with so far is something like this: > > For context, I work with Cameron, who submitted this bug. I totally agree with Peter on this. We tried to simplify the test case on our end, but the symptoms would change in odd ways. Changing the column order would change the symptoms slightly and at times the columns with DEFAULT values would be corrupt. It also seemed like string text based columns would behave differently than integers.
Commits
-
Fix possible crash with GENERATED ALWAYS columns
- a375f11c44cf 12.3 landed
- 3cb02e307e35 13.0 landed