| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Amit Langote <amitlangote09(at)gmail(dot)com> |
| Cc: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Jürgen Strobel <juergen+postgresql(at)strobel(dot)info> |
| Subject: | Re: BUG #15212: Default values in partition tables don't work as expected and allow NOT NULL violation |
| Date: | 2018-11-09 05:04:45 |
| Message-ID: | f8d48ff8-9e57-e338-e21d-74dda4eca4dc@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2018-11-09 05:11:24 | Re: BUG #15212: Default values in partition tables don't work as expected and allow NOT NULL violation |
| Previous Message | Amit Langote | 2018-11-09 04:56:36 | Re: BUG #15212: Default values in partition tables don't work as expected and allow NOT NULL violation |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2018-11-09 05:11:24 | Re: BUG #15212: Default values in partition tables don't work as expected and allow NOT NULL violation |
| Previous Message | Amit Kapila | 2018-11-09 04:58:36 | Re: Resetting PGPROC atomics in ProcessInit() |