From: Mikheev, Vadim <vmikheev@SECTORBASE.COM>
To: 'Forest Wilkinson' <fspam@home.com>
To: Philip Warner <pjw@rhyme.com.au>
To: 'Hiroshi Inoue' <Inoue@tpf.co.jp>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: RE: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1
Date: Fri, 18 May 2001 17:28:48 -0700
Message-ID: <3705826352029646A3E91C53F7189E3201662D@sectorbase2.sectorbase.com> (raw)
> I see postgres 7.1.1 is out now. Was the fix for this
> problem included in the new release?
I fear it will be in 7.2 only.
> 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?
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: vmikheev@SECTORBASE.COM, fspam@home.com, pjw@rhyme.com.au, Inoue@tpf.co.jp, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
Subject: RE: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1
In-Reply-To: <3705826352029646A3E91C53F7189E3201662D@sectorbase2.sectorbase.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox