Re: Parallel safety tagging of extension functions

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Andreas Karlsson <andreas(at)proxel(dot)se>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parallel safety tagging of extension functions
Date: 2016-05-23 17:03:47
Message-ID: 20160523170347.GA392870@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
> > On Sat, May 21, 2016 at 6:16 PM, Andreas Karlsson <andreas(at)proxel(dot)se> wrote:
> >> My immediate thought is first doing an UPDATE of pg_proc and then updating
> >> the catcache with CREATE OR REPLACE with the new arguments. Does that work?
> >> Is there a less ugly way to accomplish this?
>
> > Isn't it better to just drop and recreate the function? pageinspect
> > did so for example for heap_page_items in 1.4 to update its OUT
> > arguments.
>
> You'd have to alter the index opfamily to disconnect the function from it,
> drop/recreate the function, then re-add it to the opfamily. Kind of icky,
> but probably better than the alternatives.

What happens if the upgraded database contains indexes using those
opfamilies? I suppose getting such indexes dropped because of ALTER
EXTENSION UPDATE is not very nice.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-05-23 17:10:29 Re: Changed SRF in targetlist handling
Previous Message David G. Johnston 2016-05-23 16:56:56 Re: Re: Request for Patch Feedback: Lag & Lead Window Functions Can Ignore Nulls