Re: pg_upgrade error regarding hstore operator

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: parihaaraka <parihaaraka(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: pg_upgrade error regarding hstore operator
Date: 2016-05-24 16:17:21
Message-ID: 1125.1464106641@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

parihaaraka <parihaaraka(at)gmail(dot)com> writes:
> I have the same issue after pg_upgrade from 9.3 to 9.5.
> pg_dump generates excess commands like
> CREATE OPERATOR FAMILY bit_ops USING gin;
> ...
> while all of this is done during CREATE EXTENSION

This is fixed in the latest round of minor releases, but not in a way that
will help you if you already pg_upgrade'd such an extension:

http://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=6cead413b

Per the comments there, you could manually add that operator family back
to its extension, or just ignore the duplicate-opfamily complaints you'd
get during a restore.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2016-05-24 16:17:38 Re: FIRST_VALUE: need to group by argument?
Previous Message Manuel Gómez 2016-05-24 16:12:59 Re: FIRST_VALUE: need to group by argument?

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2016-05-24 16:24:44 Re: Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold <
Previous Message Christoph Berg 2016-05-24 16:14:09 Re: LSN as a recovery target