pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Hiroshi Inoue <Inoue@tpf.co.jp>
To: Mikheev, Vadim <vmikheev@SECTORBASE.COM>
Cc: Philip Warner <pjw@rhyme.com.au>
Cc: 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, 30 Mar 2001 19:15:22 +0900
Message-ID: <3AC45CBA.8CDC3213@tpf.co.jp> (raw)
References: <8F4C99C66D04D4118F580090272A7A234D335E@sectorbase1.sectorbase.com>

"Mikheev, Vadim" wrote:
> 
> > > >> 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?
> 
> 95% -:)
> 
> > I doubt if it's a bug of SELECT. Well what
> > 'concurrent UPDATE then SELECT FOR UPDATE +
> > SELECT' return ?
> 
> I'm going to add additional check to heapgettup and
> heap_fetch:
>

SELECT seems to be able to return a different result
from that of preceding SELECT FOR UPDATE even after
applying your change.
SELECT doesn't seem guilty but the result is far 
from intuitive.
It seems impossoble for all queires inside such
a function to use a common snapshot.

regards,
Hiroshi Inoue



view thread (21+ messages)  latest in thread

Message-ID: <3AC45CBA.8CDC3213@tpf.co.jp>
Permalink:  ../3AC45CBA.8CDC3213@tpf.co.jp/
Also on:    postgresql.org/message-id/3AC45CBA.8CDC3213@tpf.co.jp

 · 

reply

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: Inoue@tpf.co.jp, vmikheev@SECTORBASE.COM, pjw@rhyme.com.au, 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: <3AC45CBA.8CDC3213@tpf.co.jp>

* 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