Re: modify custom variables

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Vincent Mora <vincent(dot)mora(at)oslandia(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: modify custom variables
Date: 2014-06-20 16:22:56
Message-ID: 6787.1403281376@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Vincent Mora <vincent(dot)mora(at)oslandia(dot)com> writes:
> If I understand the problem correctly, on upgrate (ALTER EXTENSION), the
> old postgis library is already loaded, the old spatial functions are
> replaced by new ones pointing to the new postgis library, a call to
> DefineCustomStringVariable is made and:

> ERROR: attempt to redefine parameter "postgis.backend"

> I need to redefine the assign hook such that is calls the new library
> backend and not the old one.

I think what you need to do is arrange the upgrade process so that the old
shared library doesn't get loaded in the same session as the new one.
Otherwise, you're likely to have lots more problems than just this.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-06-20 17:01:30 Shouldn't pg_(sh)seclabel.provider be marked NOT NULL?
Previous Message Joey Caughey 2014-06-20 15:26:56 JSON and Postgres Variable Queries