pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Hiroshi Inoue <Inoue@tpf.co.jp>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Philip Warner <pjw@rhyme.com.au>
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: Wed, 28 Mar 2001 15:19:05 +0900
Message-ID: <3AC18259.C5A8B0A9@tpf.co.jp> (raw)
References: <01032713101600.07241@bartok>
	<01032713101600.07241@bartok>
	<3.0.5.32.20010328101405.02b57790@mail.rhyme.com.au>
	<16115.985739416@sss.pgh.pa.us>

Tom Lane wrote:
> 
> Philip Warner <pjw@rhyme.com.au> writes:
> >> The workaround for Forest is to make the final SELECT be a SELECT FOR
> >> UPDATE, so that it's playing by the same rules as the earlier commands.
> 
> > Eek. Does this seem good to you?
> 
> I did call it a workaround ;-)
> 
> I don't think that we dare try to make any basic changes in MVCC for 7.1
> at this late hour, so Forest is going to have to live with that answer
> for awhile.  But I would like to see a cleaner answer in future
> releases.

Is it the MVCC's restriction that each query inside a function
must use the same snapshot ?

> As I've opined before, the whole EvalPlanQual mechanism
> strikes me as essentially bogus in any case...
> 

How would you change it ? UPDATE/SELECT FOR UPDATE have to
SELECT/UPDATE the latest tuples. I don't think of any simple
way for 'SELECT FOR UPDATE' to have the same visibility as
simple SELECT.

regards,
Hiroshi Inoue



view thread (21+ messages)  latest in thread

Message-ID: <3AC18259.C5A8B0A9@tpf.co.jp>
Permalink:  ../3AC18259.C5A8B0A9@tpf.co.jp/
Also on:    postgresql.org/message-id/3AC18259.C5A8B0A9@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, tgl@sss.pgh.pa.us, pjw@rhyme.com.au, pgsql-hackers@postgresql.org
  Subject: Re: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1
  In-Reply-To: <3AC18259.C5A8B0A9@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