From: Mikheev, Vadim <vmikheev@SECTORBASE.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: Thu, 29 Mar 2001 19:14:39 -0800
Message-ID: <8F4C99C66D04D4118F580090272A7A234D335D@sectorbase1.sectorbase.com> (raw)
> >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
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, 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: <8F4C99C66D04D4118F580090272A7A234D335D@sectorbase1.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