Re: Problems with pg_upgrade after change of unix user running db.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Benedikt Grundmann <bgrundmann(at)janestreet(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Problems with pg_upgrade after change of unix user running db.
Date: 2016-10-03 14:30:36
Message-ID: 28385.1475505036@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Benedikt Grundmann <bgrundmann(at)janestreet(dot)com> writes:
> On 3 October 2016 at 14:12, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> You're going to need to manually drop that operator from the source
>> database, as "=>" isn't a legal operator name anymore. This appears
>> to be left over from a pre-9.0 version of hstore.

> Thanks for the quick reply. How do I do that however? Without dropping
> the extension itself that is:
>
> proddb_testing=# drop operator => (text, text);
> ERROR: cannot drop operator =>(text,text) because extension hstore requires it
> HINT: You can drop extension hstore instead.
>
> Is it possible that I need to do some form of hstore extension upgrade
> dance?

Ah, I'd been guessing that the operator was "loose", but if you still
have hstore 1.0 installed then yes that's the behavior I'd expect.
You need to do "alter extension hstore update". In a 9.2 database
that should bring it to 1.1 which will get rid of the operator.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Benedikt Grundmann 2016-10-03 14:38:41 Re: Problems with pg_upgrade after change of unix user running db.
Previous Message Benedikt Grundmann 2016-10-03 14:11:08 Re: Problems with pg_upgrade after change of unix user running db.