Re: DO ... RETURNING - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: DO ... RETURNING
Date
Msg-id 20130611144554.GO7200@tamriel.snowman.net
Whole thread Raw
In response to Re: DO ... RETURNING  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: DO ... RETURNING  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: DO ... RETURNING  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-hackers
* Merlin Moncure (mmoncure@gmail.com) wrote:
> I agree with all your comments pretty much down the line.  Need top
> level CALL that supports parameterization and multiple sets that
> utilizes background worker (we have example spi worker that gives some
> hints about how pl/pgsql could be made to work).  Because it's top
> level (can't even be inlined to CTE), we can access behaviors that are
> not possible in current pl/pgsql, for example setting transaction
> isolation in advance of snapshot and changing database connection
> mid-procedure.

And this still has next-to-nothing to do with the specific proposal that
was put forward.

I'd like actual procedures too, but it's a completely different and
distinct thing from making DO blocks able to return something.
Thanks,
    Stephen

pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: DO ... RETURNING
Next
From: Tatsuo Ishii
Date:
Subject: Re: Parallell Optimizer