Skip site navigation (1) Skip section navigation (2)

Re: BUG #3048: pg_dump dumps intarray metadata incorrectly

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Dmitry Koterov" <d(at)koterov(dot)ru>
Cc: pgsql-bugs(at)postgresql(dot)org, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Teodor Sigaev <teodor(at)sigaev(dot)ru>
Subject: Re: BUG #3048: pg_dump dumps intarray metadata incorrectly
Date: 2007-02-23 16:16:58
Message-ID: 280.1172247418@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"Dmitry Koterov" <d(at)koterov(dot)ru> writes:
> [ pg_restore fails with ]
> ERROR:  could not make operator class "gin__int_ops" be default for type
> pg_catalog.int4[]
> DETAIL:  Operator class "_int4_ops" already is the default.

Yeah.  I'd say that intarray's attempt to override the default status of
the built-in gin opclass is simply a bad idea and should be removed.
It's not even documented that it does that (in fact I see no mention of
GIN at all in README.intarray :-(, so we have a documentation lack
here too).

Comments?

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2007-02-23 16:35:20
Subject: Re: BUG #3038: information_schema.constraint_column_usage has wrong information for foreign keys
Previous:From: Zdenek KotalaDate: 2007-02-23 16:15:57
Subject: Re: BUG #2969: Inaccuracies in Solaris FAQ

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group