Re: MV patch broke users of ExplainOneQuery_hook

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Kevin Grittner <kgrittn(at)ymail(dot)com>
Subject: Re: MV patch broke users of ExplainOneQuery_hook
Date: 2013-04-09 14:25:35
Message-ID: 16843.1365517535@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> The materialized views patch adjusted ExplainOneQuery to take an
> additional DestReceiver argument, but failed to add a matching
> argument to the definition of ExplainOneQuery_hook. This makes the
> hook unusable. The idea of this hook is that your hook function will
> do something before and/or after calling pg_plan_query and
> ExplainOnePlan. But this no longer works, because ExplainOnePlan
> needs the DestReceiver, which hasn't been exposed to the hook. :-(

TBH I'd like to revert all of that anyway; it seemed to me to be
basically gratuitous breakage of an API used by plugins. I've not
had time to look at whether there was an actual reason for it and
if so how we might solve that differently.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2013-04-09 14:28:53 Re: MV patch broke users of ExplainOneQuery_hook
Previous Message Kevin Grittner 2013-04-09 14:11:19 Re: MV patch broke users of ExplainOneQuery_hook