From: Forest Wilkinson <fspam@home.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Mikheev, Vadim <vmikheev@SECTORBASE.COM>
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 15:47:22 -0800
Message-ID: <01033015472200.01012@bartok> (raw)
In-Reply-To: <189.985932915@sss.pgh.pa.us>
References: <3.0.5.32.20010330140228.01f9d100@mail.rhyme.com.au>
<3AC40890.399F5102@tpf.co.jp>
<189.985932915@sss.pgh.pa.us>
On Thursday 29 March 2001 22:15, Tom Lane wrote:
> > Just looked in heapam.c - I can fix it in two hours.
> > The question is - should we do this now?
>
> This scares the hell out of me.
>
> I do NOT think we should be making quick-hack changes in fundamental
> system semantics at this point of the release cycle.
Although I'm the one who is being bit by this bug, I tend to agree.
> The problem went unnoticed for two full release cycles
I first reported the problem on 25 September 2000, on the pgsql-sql list,
message subject "SQL functions not locking properly?" I was using 7.0.2 at
the time. Also, I seem to remember that a problem of this nature bit me in
6.5.x as well.
> it can wait another cycle for a fix that has been considered, reviewed,
> and tested. Let's not risk making things worse by releasing a new
> behavior we might find out is also wrong.
Good point. How long is the next cycle likely to take?
Forest
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: fspam@home.com, tgl@sss.pgh.pa.us, vmikheev@SECTORBASE.COM, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1
In-Reply-To: <01033015472200.01012@bartok>
* 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