Date: Fri, 9 Nov 2018 18:42:28 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: =?utf-8?Q?J=C3=BCrgen?= 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>
Subject: Re: BUG #15212: Default values in partition tables don't work as
 expected and allow NOT NULL violation
Message-ID: <20181109214228.faadf3xh6haphi6x@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <553783fa-c48f-629a-daa9-602599deb516@strobel.info>
User-Agent: NeoMutt/20180716
Precedence: bulk

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