Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1

From: Forest Wilkinson <fspam(at)home(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
Cc: pgsql-sql(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1
Date: 2001-03-30 23:47:22
Message-ID: 01033015472200.01012@bartok (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-sql
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

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2001-03-31 00:01:27
Subject: Re: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1
Previous:From: Henry B. HotzDate: 2001-03-30 22:08:28
Subject: MacOS X OK, was: Call for platforms

pgsql-sql by date

Next:From: Tom LaneDate: 2001-03-31 00:01:27
Subject: Re: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1
Previous:From: Najm HashmiDate: 2001-03-30 22:01:51
Subject: pg_dump error plus RelationBuildTriggers: 1 record(s) not found for rel links

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group