Re: Extension upgrade and GUCs

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Paul Ramsey <pramsey(at)cleverelephant(dot)ca>
Cc: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Extension upgrade and GUCs
Date: 2015-08-20 09:17:31
Message-ID: CANP8+jL=vAgmeq_dQ3UOC90rtZu0M=KS_9tG4cVS+qWCVhf5mA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 18 August 2015 at 21:03, Paul Ramsey <pramsey(at)cleverelephant(dot)ca> wrote:

> So I need a way to either (a) notice when I already have a (old) copy
> of the library loaded and avoid trying to setup the GUC in that case
> or (b) set-up the GUC in a somewhat less brittle way than
> DefineCustomStringVariable() allows, something that can overwrite
> things instead of just erroring out.
>

Are you trying to preserve the in-memory state across upgrade as well? It
sounds unlikely we can support that directly in the general case.

Sounds like we need RedefineCustomStringVariable()

--
Simon Riggs http://www.2ndQuadrant.com/
<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 Pavan Deolasee 2015-08-20 09:27:50 Re: Declarative partitioning
Previous Message Amit Langote 2015-08-20 09:10:20 Re: Declarative partitioning