pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Hiroshi Inoue <Inoue@tpf.co.jp>
To: Philip Warner <pjw@rhyme.com.au>
Cc: Mikheev, Vadim <vmikheev@SECTORBASE.COM>
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 13:16:16 +0900
Message-ID: <3AC40890.399F5102@tpf.co.jp> (raw)
References: <3.0.5.32.20010330140228.01f9d100@mail.rhyme.com.au>

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?
> 

I doubt if it's a bug of SELECT. Well what
'concurrent UPDATE then SELECT FOR UPDATE +
SELECT' return ?

regards,
Hiroshi Inoue



view thread (21+ messages)  latest in thread

Message-ID: <3AC40890.399F5102@tpf.co.jp>
Permalink:  ../3AC40890.399F5102@tpf.co.jp/
Also on:    postgresql.org/message-id/3AC40890.399F5102@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, pjw@rhyme.com.au, vmikheev@SECTORBASE.COM, 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: <3AC40890.399F5102@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