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

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "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 06:15:15
Message-ID: 189.985932915@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-sql
> 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.

The problem went unnoticed for two full release cycles --- therefore,
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.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Thomas LockhartDate: 2001-03-30 06:17:31
Subject: Re: Unsigned int functions
Previous:From: Philip WarnerDate: 2001-03-30 06:14:54
Subject: Re: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1

pgsql-sql by date

Next:From: Thomas LockhartDate: 2001-03-30 06:22:21
Subject: Re: [PATCHES] Error in the date field (with NULL value...).Thanks!
Previous:From: Philip WarnerDate: 2001-03-30 06:14:54
Subject: Re: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1

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