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
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-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

Browse pgsql-hackers by date

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

Browse pgsql-sql by date

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