Re: Parallel safety tagging of extension functions

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Andreas Karlsson <andreas(at)proxel(dot)se>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parallel safety tagging of extension functions
Date: 2016-06-09 17:59:00
Message-ID: CA+TgmoaZKZ1YzL5A_KNmeZs6Ottp0Z3n1qs+7YU1jXncUTvZsg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jun 9, 2016 at 1:51 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Sat, May 21, 2016 at 11:45 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> Yes, let's fix it. This will also take care of the questions about
>>> whether the GIN/GIST opclass tweaks I made a few months ago require
>>> module version bumps.
>
>> Tom, there's a patch for this at
>> https://www.postgresql.org/message-id/574F091A.3050800@proxel.se which
>> I think you should review, since you were the one who made the tweaks
>> involved. Any chance you can do that RSN? If we want to get this
>> done at all, we should really get it into beta2. Also, the patches
>> Andreas posted for applying parallel-safety markings apply on top of
>> that, so that needs to go in first, at least for the affected modules.
>
> OK, I'll take it. You're done with Andreas' patches otherwise?

No. I can go through the unaffected ones in the meantime, though, and
then come back to the affected ones after you deal with this.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2016-06-09 18:05:11 Re: Rename max_parallel_degree?
Previous Message Robert Haas 2016-06-09 17:57:15 Re: [COMMITTERS] pgsql: Don't generate parallel paths for rels with parallel-restricted