Re: WIP: push AFTER-trigger execution into ModifyTable node - Mailing list pgsql-hackers

From Greg Stark
Subject Re: WIP: push AFTER-trigger execution into ModifyTable node
Date
Msg-id 407d949e0910291652t6d5c09a9ofa2b1b9c0631c24b@mail.gmail.com
Whole thread Raw
In response to Re: WIP: push AFTER-trigger execution into ModifyTable node  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: WIP: push AFTER-trigger execution into ModifyTable node
List pgsql-hackers
On Thu, Oct 29, 2009 at 7:17 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Pipelined execution would be nice but I really doubt that it's worth
> what we'd have to give up to have it.  The one-at-a-time behavior will
> be simple to understand and reliable to use.  Concurrent execution won't
> be either.

I think the ideal way to get pipelined execution will be to detect the
cases where it's safe, ie, no deletes, inserts, or updates, no
recursive calls, and only one call site, and inline the sql directly
into the callsite. Actually we could do that even if there are two
callsites if there are no volatile functions but estimating whether
that would be a win or a loss would be hard.

--
greg


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: grant with hierarchy option
Next
From: Itagaki Takahiro
Date:
Subject: Re: Syntax for partitioning