Re: clearing opfuncid vs. parallel query - Mailing list pgsql-hackers

From Robert Haas
Subject Re: clearing opfuncid vs. parallel query
Date
Msg-id CA+Tgmob6uw8bBTPaxKr8HXdMNG1+7MXKjCj7UwQRHS1DxkJ4NA@mail.gmail.com
Whole thread Raw
In response to Re: clearing opfuncid vs. parallel query  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Sep 23, 2015 at 7:25 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> On Wed, Sep 23, 2015 at 5:39 PM, Tom Lane <tgl@sss.pgh.pa.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.

Cool, thanks.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [COMMITTERS] pgsql: Lower *_freeze_max_age minimum values.
Next
From: Andres Freund
Date:
Subject: Re: clearing opfuncid vs. parallel query