From: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
---|---|
To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Rules on table partitions |
Date: | 2017-06-21 09:49:41 |
Message-ID: | CAEZATCXzSBLqDTs3vdeC1tnoG6vRWtMariNEyogTABsdqbVm0A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 20 June 2017 at 03:01, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> Hmm, yes. The following exercise convinced me.
>
> create table r (a int) partition by range (a);
> create table r1 partition of r for values from (1) to (10);
> create rule "_RETURN" as on select to r1 do instead select * from r;
>
> insert into r values (1);
> ERROR: cannot insert into view "r1"
> HINT: To enable inserting into the view, provide an INSTEAD OF INSERT
> trigger or an unconditional ON INSERT DO INSTEAD rule.
>
> The error is emitted by CheckValidResultRel() that is called on individual
> leaf partitions when setting up tuple-routing in ExecInitModifyTable.
>
> I agree that we should forbid this case, so please find attached a patch.
>
Committed.
Regards,
Dean
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Kuzmenkov | 2017-06-21 11:48:38 | Re: Proposal for CSN based snapshots |
Previous Message | Konstantin Knizhnik | 2017-06-21 09:46:05 | Re: ASOF join |