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

Re: BUG #3048: pg_dump dumps intarray metadata incorrectly

From: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dmitry Koterov <d(at)koterov(dot)ru>, pgsql-bugs(at)postgresql(dot)org, Teodor Sigaev <teodor(at)sigaev(dot)ru>
Subject: Re: BUG #3048: pg_dump dumps intarray metadata incorrectly
Date: 2007-04-06 17:45:27
Message-ID: Pine.LNX.4.64.0704062128260.12152@sn.sai.msu.ru (view raw or flat)
Thread:
Lists: pgsql-bugs
On Mon, 2 Apr 2007, Bruce Momjian wrote:

> Tom Lane wrote:
>> Bruce Momjian <bruce(at)momjian(dot)us> writes:
>>> Tom, do you want this fixed for 8.2.X?
>>
>>> Tom Lane wrote:
>>>> 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.
>>
>> I don't recall having seen a response from Oleg or Teodor, and would
>> like their input before making a final decision --- but at the moment
>> I think we should take that out.
>
> Oleg or Teodor, I need a comment on this.

We agree with Tom in this case and  we'll remove update of
system catalog. But, I want to rise the problem again - pg_dump doesn't
track changes of system catalog. The problem could be more pronounced in 
case of built-in FTS, if somebody with superuser rights changes
fts configurations in system catalog.



 	Regards,
 		Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83

In response to

Responses

pgsql-bugs by date

Next:From: Alvaro HerreraDate: 2007-04-09 19:05:08
Subject: Re: BUG #3048: pg_dump dumps intarray metadata incorrectly
Previous:From: Zdenek KotalaDate: 2007-04-04 16:52:46
Subject: Re: potential integer overflow in md.c

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