Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.3/8.11.1) with ESMTP id f2S0UVw35468; Tue, 27 Mar 2001 19:30:31 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f2S0UGw16118; Tue, 27 Mar 2001 19:30:16 -0500 (EST) To: Philip Warner cc: pgsql-sql@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1 In-reply-to: <3.0.5.32.20010328101405.02b57790@mail.rhyme.com.au> References: <01032713101600.07241@bartok> <01032713101600.07241@bartok> <3.0.5.32.20010328101405.02b57790@mail.rhyme.com.au> Comments: In-reply-to Philip Warner message dated "Wed, 28 Mar 2001 10:14:05 +1000" Date: Tue, 27 Mar 2001 19:30:16 -0500 Message-ID: <16115.985739416@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200103/568 X-Sequence-Number: 2238 Philip Warner 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. As I've opined before, the whole EvalPlanQual mechanism strikes me as essentially bogus in any case... regards, tom lane