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

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

From: Forest Wilkinson <fspam(at)home(dot)com>
To: Philip Warner <pjw(at)rhyme(dot)com(dot)au>, "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>, "'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-05-17 02:18:51
Message-ID: 01051619185100.01497@bartok (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-sql
I see postgres 7.1.1 is out now.  Was the fix for this problem included in 
the new release?

On Thursday 29 March 2001 20:02, Philip Warner wrote:
> At 19:14 29/03/01 -0800, Mikheev, Vadim wrote:
> >> >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?
> It's a bug; how confident are you of the fix?

In response to

pgsql-hackers by date

Next:From: Lincoln YeohDate: 2001-05-17 05:36:57
Subject: Re: Upgrade issue (again).
Previous:From: Christopher Kings-LynneDate: 2001-05-17 02:00:14
Subject: RE: Configurable path to look up dynamic libraries

pgsql-sql by date

Next:From: Jonathan BartlettDate: 2001-05-17 02:48:03
Subject: Re: Setting session global variables
Previous:From: Roberto MelloDate: 2001-05-17 01:26:15
Subject: Re: Give me a suggestion 'START WITH .. CONNECT BY'.

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