Re: Bug in new buffer freelist code - Mailing list pgsql-hackers

From Jan Wieck
Subject Re: Bug in new buffer freelist code
Date
Msg-id 3FFC1F93.30704@Yahoo.com
Whole thread Raw
In response to Re: Bug in new buffer freelist code  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Bug in new buffer freelist code  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:

> Jan Wieck <JanWieck@Yahoo.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@Yahoo.com #



pgsql-hackers by date:

Previous
From: "Andrew Dunstan"
Date:
Subject: Re: [PATCHES] Function argument names
Next
From: Greg Stark
Date:
Subject: Re: Brokenness in parsing of pg_hba.conf