| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: clearing opfuncid vs. parallel query |
| Date: | 2015-09-24 15:41:08 |
| Message-ID: | CA+Tgmob6uw8bBTPaxKr8HXdMNG1+7MXKjCj7UwQRHS1DxkJ4NA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 23, 2015 at 7:25 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.
Cool, thanks.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-09-24 15:43:10 | Re: clearing opfuncid vs. parallel query |
| Previous Message | Alvaro Herrera | 2015-09-24 15:39:54 | Re: [COMMITTERS] pgsql: Lower *_freeze_max_age minimum values. |