From: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Amit Langote <amitlangote09@gmail.com>
Cc: Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Jürgen Strobel <juergen+postgresql@strobel.info>
Subject: Re: BUG #15212: Default values in partition tables don't work as expected and allow NOT NULL violation
Date: Fri, 9 Nov 2018 14:04:45 +0900
Message-ID: <f8d48ff8-9e57-e338-e21d-74dda4eca4dc@lab.ntt.co.jp> (raw)
In-Reply-To: <20181108193940.2uam7tz6femqrd64@alvherre.pgsql>
References: <20181108193940.2uam7tz6femqrd64@alvherre.pgsql>
On 2018/11/09 4:39, Alvaro Herrera wrote:
> Pushed.
Thank you for committing. I've closed the CF entry.
> I included the test case for collations to the three branches, but no
> code changes. We can patch master for the handling of collations per
> your patch,
Okay, but should we back-patch it by adding WARNING to back-branches as
you suggest?
> and if somebody has it, a change to how defaults are applied
> when routing tuples.
I haven't written such a patch yet. Do we want such a feature?
Thanks,
Amit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: Langote_Amit_f8@lab.ntt.co.jp, alvherre@2ndquadrant.com, amitlangote09@gmail.com, ashutosh.bapat@enterprisedb.com, pgsql-hackers@lists.postgresql.org, juergen+postgresql@strobel.info
Subject: Re: BUG #15212: Default values in partition tables don't work as expected and allow NOT NULL violation
In-Reply-To: <f8d48ff8-9e57-e338-e21d-74dda4eca4dc@lab.ntt.co.jp>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox