Re: BUG #15212: Default values in partition tables don't work as expected and allow NOT NULL violation
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Amit Langote <amitlangote09@gmail.com>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2018-11-08T16:38:09Z
Lists: pgsql-bugs, pgsql-hackers
On 2018-Nov-09, Amit Langote wrote: > On Fri, Nov 9, 2018 at 1:03 AM Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > > On 2018-Nov-07, Amit Langote wrote: > > Hmm, I'm thinking perhaps we shouldn't backpatch this part. It's > > obviously a bug, but we might break somebody's working apps. Therefore > > I think I'd rather leave it out of the current bugfix and commit > > separately. > > Okay, that may be fine because nothing wrong is happening by silently > ignoring the partition's specified collation. Actually, how about we reduce the message to a WARNING in released branches, and ERROR in master? Broken applications would continue to work, but users might become aware that there might be a problem. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Revise attribute handling code on partition creation
- e0c05bf4a7e6 11.2 landed
- 705d433fd5e2 12.0 landed
- 21c9e4973cec 10.7 landed