From: | Dean Rasheed <dean_rasheed(at)hotmail(dot)com> |
---|---|
To: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, <pgsql-hackers(at)postgresql(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com> |
Subject: | Re: Auto-explain patch |
Date: | 2008-08-31 09:04:45 |
Message-ID: | BAY102-W270D92DBFAD83E0B24919FF25D0@phx.gbl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> * auto_explain.tgz
> A contrib module version of auto-explain.
> An arguable part is initializing instruments in ExecutorRun_hook.
> The initialization should be done in ExecutorStart normally, but
> it is too late in the hook. Is it safe? or are there any better idea?
> README is a plain-text for now, and I'll rewrite it in sgml if needed.
>
How about adding a new hook to control instrumentation of queries in
ExecutorStart? Something like:
typedef bool (*ExecutorDoInstrument_hook_type) (QueryDesc *queryDesc, int eflags);
extern PGDLLIMPORT ExecutorDoInstrument_hook_type ExecutorDoInstrument_hook;
I think that would allow your module code to be simplified,
and it would allow other future extensions to hook in and
enable instrumentation before queries are run.
Regards, Dean.
_________________________________________________________________
Win a voice over part with Kung Fu Panda & Live Search and 100’s of Kung Fu Panda prizes to win with Live Search
http://clk.atdmt.com/UKM/go/107571439/direct/01/
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2008-08-31 09:27:47 | rmgr hooks and contrib/rmgr_hook |
Previous Message | Gregory Stark | 2008-08-31 05:27:27 | Re: Attaching error cursor position to invalid constant values |