Re: MV patch broke users of ExplainOneQuery_hook

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

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> If we don't revert then what you pushed is clearly necessary, so
> no objection to having done that.  I'll look at the larger
> situation as soon as I get a chance.

Any objections to my pushing the patch I posted Friday to draw a
distinction between populated and scannable, which also attempted
to address a couple points raised by you, or would you rather the
code didn't change at the moment?

--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-04-09 15:40:48 Re: MV patch broke users of ExplainOneQuery_hook
Previous Message Andrew Dunstan 2013-04-09 15:06:19 sql_drop event trigger vs buildfarm