Re: Bug in new buffer freelist code

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Bug in new buffer freelist code
Date: 2004-01-07 15:02:43
Message-ID: 3FFC1F93.30704@Yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

> Jan Wieck <JanWieck(at)Yahoo(dot)com> writes:
>> Yeah, looks like ... but I actually want to have a clean reproduction of
>> the error before I attempt to fix it.
>
> Well, I can tell you that just running "make check" over and over isn't
> a real efficient way to reproduce the problem. It might work to do
> something like stopping a FlushRelationBuffers call in its tracks with
> the debugger, meanwhile accessing the same rel with another backend.

So far I was not able to reproduce the problem. If it is what we think,
then it should be possible to reproduce it with just one single DB
connection, no?

Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruno Wolff III 2004-01-07 15:46:55 Re: Paypal WAS: PostgreSQL speakers needed for OSCON
Previous Message Andrew Dunstan 2004-01-07 13:48:49 Re: [PATCHES] Function argument names