Re: Single row INSERT on updatable VIEW on top of partitioned table is run against each inheriting table, giving multiple rows from single insert. - Mailing list pgsql-bugs

From Terje Elde
Subject Re: Single row INSERT on updatable VIEW on top of partitioned table is run against each inheriting table, giving multiple rows from single insert.
Date
Msg-id 1297A7EB-DA4B-44A0-A768-84A094EFF230@elde.net
Whole thread Raw
In response to Single row INSERT on updatable VIEW on top of partitioned table is run against each inheriting table, giving multiple rows from single insert.  (Terje Elde <terje@elde.net>)
List pgsql-bugs
On Jul 24, 2013, at 2:37 PM, Terje Elde <terje@elde.net> wrote:
> Short summary:
> If I run a single INSERT against an updateable VIEW on top of a =
partitioned table, it's run against all the tables/partitions.  I'd =
expect that with UPDATE and DELETE, but not with INSERT.  Result is =
multiple rows for a single INSERT, one for each table.

Sorry, while I did scan the last month and the open issues-list before =
sending, I missed that this had already been identified, patch =
submitted, and applied:

=
http://www.postgresql.org/message-id/CAEZATCW4EUi-BqjzYyow0nt84jhOwSDxzbht=
bFoRrvUi59NCnQ@mail.gmail.com
http://www.postgresql.org/message-id/11683.1372868994@sss.pgh.pa.us

Everything behaves as expected with the patch.

Terje

pgsql-bugs by date:

Previous
From: Terje Elde
Date:
Subject: Single row INSERT on updatable VIEW on top of partitioned table is run against each inheriting table, giving multiple rows from single insert.
Next
From: chmelarp@fit.vutbr.cz
Date:
Subject: BUG #8329: UPDATE x SET x.y = x.y + z does not work in PL/pgSQL