From: | Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi> |
---|---|
To: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Writeable CTEs and side effects |
Date: | 2009-10-07 21:20:20 |
Message-ID: | 4ACD0614.30800@cs.helsinki.fi |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jaime Casanova wrote:
> On Wed, Oct 7, 2009 at 4:08 PM, Marko Tiikkaja
> <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi> wrote:
>> 1) WITH t AS
>> (UPDATE foo SET bar = bar+1 RETURNING *)
>> SELECT * FROM t LIMIT 1;
>>
>> What's problematic here is that only 1 row is read from the CTE, meaning
>> also that only one row is updated which, at least how I see it, is not
>> what we want. The CTE should only store one row and return that after
>> it has completely processed the UPDATE statement.
>>
>
> i'm talking from my ignorance... but AFAIU this should process the
> whole UPDATE and then form a WorkTable with the results...
> what the select reads from that results is another thing...
>
Right. This is exactly what I'm trying to do, except I think we could
easily optimize this case and store only the first processed row inside
the CTE.
Regards,
Marko Tiikkaja
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2009-10-07 21:22:21 | Re: Writeable CTEs and side effects |
Previous Message | Brad T. Sliger | 2009-10-07 21:18:58 | Re: Unicode UTF-8 table formatting for psql text output |