| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: NOT NULL constraints on range partition key columns |
| Date: | 2017-05-15 19:29:02 |
| Message-ID: | CA+TgmoayJEAKXM+_dSHH07s-+_CL4NWdrgeyVq9AejrzTYaO+A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 15, 2017 at 9:12 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> Can't we allow NULL to get inserted into the partition (leaf
> partition) if the user uses the partition name in Insert statement?
That would be terrible behavior - the behavior of tuple routing should
match the enforced constraints.
> For root partitions, I think for now giving an error is okay, but once
> we have default partitions (Rahila's patch), we can route NULLS to
> default partition.
Yeah, that's exactly why I think we should make the change Amit is
proposing here. If we don't, then we won't be able to accept NULL
values even after we have the default partitioning stuff.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Dilger | 2017-05-15 19:32:29 | Re: Hash Functions |
| Previous Message | Robert Haas | 2017-05-15 19:26:02 | Re: Hash Functions |