Re: [PATCHES] WIP: executor_hook for pg_stat_statements

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCHES] WIP: executor_hook for pg_stat_statements
Date: 2008-07-08 12:16:31
Message-ID: 1215519391.4051.876.camel@ebony.2ndQuadrant
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches


On Mon, 2008-07-07 at 10:51 -0400, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > On Mon, 2008-07-07 at 11:03 +0900, ITAGAKI Takahiro wrote:
> >> 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.
>
> I don't want the tag there at all, much less converted to a pointer.
> What would the semantics be of copying the node, and why?
>
> Please justify why you must have this and can't do what you want some
> other way.

Agreed. If we have plugins for planner and executor we should be able to
pass information around in the background. We have mechanisms for two
plugins to rendezvous, so we can use that if they're completely separate
plugins.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Treat 2008-07-08 12:38:11 Re: CommitFest rules
Previous Message Zdenek Kotala 2008-07-08 11:23:50 Re: [WIP] patch - Collation at database level

Browse pgsql-patches by date

  From Date Subject
Next Message Alvaro Herrera 2008-07-08 13:32:44 Re: [PATCHES] Extending grant insert on tables to sequences
Previous Message Tatsuo Ishii 2008-07-08 09:01:05 Re: [PATCHES] WITH RECURSIVE updated to CVS TIP