RE: DeadLockCheck is buggy - Mailing list pgsql-hackers

From Mikheev, Vadim
Subject RE: DeadLockCheck is buggy
Date
Msg-id 8F4C99C66D04D4118F580090272A7A234D3288@sectorbase1.sectorbase.com
Whole thread Raw
In response to DeadLockCheck is buggy  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> > I have been studying DeadLockCheck for most of a day now, 
> > and I doubt that this is the only bug lurking in it.
> > I think that we really ought to throw it away and start
> > over, because it doesn't look to me at all like a standard
> > deadlock-detection algorithm.  The standard way of doing
> 
> Go ahead.  Throw away my code.  *sniff*  :-)

And my changes from the days of 6.5 -:)

Vadim


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: SIGTERM -> elog(FATAL) -> proc_exit() is probably a bad idea
Next
From: Hunter Hillegas
Date:
Subject: Re: [GENERAL] Slashdot and PostgreSQL