From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Using results from INSERT ... RETURNING |
Date: | 2009-10-04 12:15:11 |
Message-ID: | 603c8f070910040515j5b7bc050k60472316b2432108@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Oct 4, 2009 at 8:14 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Marko -
>
> I noticed something a little odd about the new append-plan handling.
>
> rhaas=# explain update parent set c = 1;
> QUERY PLAN
> -----------------------------------------------------------------------
> Update (cost=0.00..60.80 rows=4080 width=12)
> -> Seq Scan on parent (cost=0.00..31.40 rows=2140 width=10)
> -> Seq Scan on child parent (cost=0.00..29.40 rows=1940 width=14)
> (3 rows)
>
> That may be OK, actually, but it does look a little weird.
Argh. Nevermind. It was like that before.
Sigh.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Tiikkaja | 2009-10-04 13:33:50 | Re: Using results from INSERT ... RETURNING |
Previous Message | Robert Haas | 2009-10-04 12:14:23 | Re: Using results from INSERT ... RETURNING |