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

RE: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1

From: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
To: "'Philip Warner'" <pjw(at)rhyme(dot)com(dot)au>, "'Hiroshi Inoue'" <Inoue(at)tpf(dot)co(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-sql(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: RE: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1
Date: 2001-03-30 03:14:39
Message-ID: 8F4C99C66D04D4118F580090272A7A234D335D@sectorbase1.sectorbase.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-sql
> >Reported problem is caused by bug (only one tuple version must be
> >returned by SELECT) and this is way to fix it.
> >
> 
> I assume this is not possible in 7.1?

Just looked in heapam.c - I can fix it in two hours.
The question is - should we do this now?
Comments?

Vadim

pgsql-hackers by date

Next:From: Mark KnoxDate: 2001-03-30 03:33:42
Subject: Re: Re: Call for platforms
Previous:From: Bruce MomjianDate: 2001-03-30 03:12:45
Subject: User administration tool

pgsql-sql by date

Next:From: Philip WarnerDate: 2001-03-30 04:02:28
Subject: RE: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1
Previous:From: Philip WarnerDate: 2001-03-30 02:49:11
Subject: RE: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1

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