| From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
|---|---|
| To: | "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | RE: DeadLockCheck is buggy |
| Date: | 2001-01-17 17:25:49 |
| Message-ID: | 8F4C99C66D04D4118F580090272A7A234D3288@sectorbase1.sectorbase.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2001-01-17 17:58:54 | Re: Re: Performance degradation in PostgreSQL 7.1beta3 vs |
| Previous Message | Hannu Krosing | 2001-01-17 17:22:09 | Re: Re: Performance degradation in PostgreSQL 7.1beta3 vs 6.5.3 |