Re: BUG #3048: pg_dump dumps intarray metadata incorrectly

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Dmitry Koterov <d(at)koterov(dot)ru>, 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-03-27 01:53:51
Message-ID: 200703270153.l2R1rp428783@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


Tom, do you want this fixed for 8.2.X?

---------------------------------------------------------------------------

Tom Lane wrote:
> "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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2007-03-27 02:11:34 Re: BUG #3048: pg_dump dumps intarray metadata incorrectly
Previous Message Magnus Hagander 2007-03-24 22:20:33 Re: BUG #3123: Problem with LDAP auth strings