Re: pgsql: Fix pg_dump so pg_upgrade'ing an extension with simple opfamilie

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Fix pg_dump so pg_upgrade'ing an extension with simple opfamilie
Date: 2016-04-14 01:42:10
Message-ID: 20160414014210.GW10850@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> > Fix pg_dump so pg_upgrade'ing an extension with simple opfamilies works.
>
> I see this has broken the buildfarm's pg_upgrade checks, though only in
> HEAD which makes me suspicious that it's exposing a pre-existing bug.
> Odd, because I definitely tested pg_upgrade here. Will dig into it
> later this evening.

My test shows, near the end:

ERROR: zero-length delimited identifier at or near """" at character 40
STATEMENT: CREATE OPERATOR FAMILY "box_ops" USING "";

Not immediately seeing why it's unable to find the amname for box_ops
though.

Thanks!

Stephen

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Fujii Masao 2016-04-14 02:17:57 pgsql: Fix duplicated index entry in doc.
Previous Message Stephen Frost 2016-04-14 01:31:36 pgsql: Disallow SET SESSION AUTHORIZATION pg_*