Re: clearing opfuncid vs. parallel query

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>
Subject: Re: clearing opfuncid vs. parallel query
Date: 2015-09-23 23:25:24
Message-ID: 3833.1443050724@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:
> On Wed, Sep 23, 2015 at 5:39 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Yeah, though I think of that as a longer-term issue, ie we could clean it
>> up sometime later.

> So, you're thinking of something as simple as the attached?

Right. I'll make a mental to-do to see about getting rid of set_opfuncid
later.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-09-23 23:30:17 Re: Bad row estimation with indexed func returning bool
Previous Message Robert Haas 2015-09-23 23:10:37 Re: clearing opfuncid vs. parallel query