On Wed, Jul 26, 2017 at 5:43 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > I have not been paying any attention to this thread whatsoever, > but I wonder if you can address your problem by building on top of > the ExecProcNode replacement that Andres is working on, > https://www.postgresql.org/message-id/20170726012641.bmhfcp5ajpudi...@alap3.anarazel.de > > The scheme he has allows $extra_stuff to be injected into ExecProcNode at > no cost when $extra_stuff is not needed, because you simply don't insert > the wrapper function when it's not needed. I'm not sure that it will > scale well to several different kinds of insertions though, for instance > if you wanted both instrumentation and async support on the same node. > But maybe those two couldn't be arms-length from each other anyway, > in which case it might be fine as-is.
Yeah, I don't quite see how that would apply in this case -- what we need here is not as simple as just conditionally injecting an extra bit. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers