Re: [PATCHES] WIP: executor_hook for pg_stat_statements - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: [PATCHES] WIP: executor_hook for pg_stat_statements
Date
Msg-id 1215414601.4051.432.camel@ebony.site
Whole thread Raw
In response to Re: [PATCHES] WIP: executor_hook for pg_stat_statements  (ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp>)
Responses Re: [PATCHES] WIP: executor_hook for pg_stat_statements
List pgsql-hackers
On Mon, 2008-07-07 at 11:03 +0900, ITAGAKI Takahiro wrote:
> Simon Riggs <simon@2ndquadrant.com> wrote:
> 
> > > The attached patch (executor_hook.patch) modifies HEAD as follows.
> > > 
> > > - Add "tag" field (uint32) into PlannedStmt.
> > > - Add executor_hook to replace ExecutePlan().
> > > - Move ExecutePlan() to a global function.
> > 
> > The executor_hook.patch is fairly trivial and I see no errors.
> > 
> > The logic of including such a patch is clear. If we have a planner hook
> > then we should also have an executor hook.
> 
> One issue is "tag" field. The type is now uint32. It's enough in my plugin,
> but if some people need to add more complex structures in PlannedStmt,
> Node type would be better rather than uint32. Which is better?

I was imagining that tag was just an index to another data structure,
but probably better if its a pointer.

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Training, Services and Support



pgsql-hackers by date:

Previous
From:
Date:
Subject: pg_ctl -w with postgresql.conf in non-default path
Next
From: Yoshiyuki Asaba
Date:
Subject: Re: [PATCHES] WITH RECURSIVE updated to CVS TIP