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

Re: VACUUM/t_ctid bug (was Re: GiST concurrency commited)

From: Teodor Sigaev <teodor(at)sigaev(dot)ru>
To: Mario Weilguni <mweilguni(at)sime(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: VACUUM/t_ctid bug (was Re: GiST concurrency commited)
Date: 2005-08-30 10:19:38
Message-ID: 431432BA.9030207@sigaev.ru (view raw or flat)
Thread:
Lists: pgsql-hackers
> Since 7.4 we have troubles with ltree (seldom corruption of buffer cache, not 
> on-disk), might this bug be somehow related to the ltree problem?
> 7.2 was rock-stable with ltree.

Not sure. Fixed bug was (@ - contains operation):

update wow set a = a || '{101}'::int[] where a @ '{1,2,3}';
select a from wow where a @ '{1,2,3}' and not a @ '{101}';

After update query select must not find any rows, but it did. The problem was in 
GiST code and so any GiST idexes was affected.

Can you say more about your trouble?


-- 
Teodor Sigaev                                   E-mail: teodor(at)sigaev(dot)ru
                                                    WWW: http://www.sigaev.ru/

In response to

Responses

pgsql-hackers by date

Next:From: Mario WeilguniDate: 2005-08-30 10:51:44
Subject: Re: VACUUM/t_ctid bug (was Re: GiST concurrency commited)
Previous:From: Mario WeilguniDate: 2005-08-30 09:58:37
Subject: Re: VACUUM/t_ctid bug (was Re: GiST concurrency commited)

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