From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCHES] WIP: executor_hook for pg_stat_statements |
Date: | 2008-07-15 08:31:29 |
Message-ID: | 1216110689.19656.132.camel@ebony.2ndQuadrant |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Tue, 2008-07-15 at 16:25 +0900, ITAGAKI Takahiro wrote:
> > > Also, after looking at the patch more closely, was there a good
> reason
> > > for making the hook intercept ExecutePlan rather than ExecutorRun?
> >
> > That raises the question of whether we should have ExecutorStart()
> and
> > ExecutorEnd() hooks as well, to round things off.
>
> Yeah, and also ExecutorRewind() hook. There are 4 interface functions
> in executor. My addin only needs Run hook because it doesn't modify
> the actual behavior of executor. However, when someone hope to replace
> the behavior, they need all of the hooks. (Is multi-threaded executor
> project still alive?)
No plans here, just thinking: if we do it, do it once.
The reason I wasn't thinking about the rewind part though was it seems
like someone might want to set up or tear down something at appropriate
times, so adding Start/End felt "obvious". Yes, lets have Rewind also.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2008-07-15 09:29:54 | Re: [GENERAL] Fragments in tsearch2 headline |
Previous Message | Heikki Linnakangas | 2008-07-15 08:23:50 | Re: [PATCHES] VACUUM Improvements - WIP Patch |
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2008-07-15 09:10:37 | Re: \d+ should display the storage options for columns |
Previous Message | Heikki Linnakangas | 2008-07-15 08:23:50 | Re: [PATCHES] VACUUM Improvements - WIP Patch |