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: Jürgen Strobel <juergen+postgresql@strobel.info>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, Amit Langote <amitlangote09@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2018-11-09T21:42:28Z
Lists: pgsql-bugs, pgsql-hackers
On 2018-Nov-09, Jürgen Strobel wrote:

> OK got it. I agree about differing COLLATE clauses making no sense and
> with the ERROR+WARNING solution, but I didn't report that.

Yeah, I happened to notice it on code inspection.

> The NULL violation is obvious too.

Yeah, IMO that was an obvious bugfix.

> I still hope for a bug fix for the DEFAULT clause with sensible
> restrictions.

Yeah, I understand that this is the one that you really care about.
However, I think a fix is unlikely to be back-patchable, because it may
break existing applications that are written to expect the current
behavior.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


Commits

  1. Revise attribute handling code on partition creation