| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Rick Gigger <rick(at)alpinenetworking(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: panic on 7.3 |
| Date: | 2006-01-21 01:25:35 |
| Message-ID: | 7111.1137806735@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> If this theory is correct, the bug has been there since the clog code
> was first written. But the conditions for having it happen are narrow
> enough that it's not too surprising we haven't seen it before.
Actually, there seem to be a couple of unresolved bug reports that look
like the same thing ...
http://archives.postgresql.org/pgsql-hackers/2006-01/msg00216.php
http://archives.postgresql.org/pgsql-bugs/2005-12/msg00130.php
http://archives.postgresql.org/pgsql-general/2005-10/msg00975.php
The spelling of the message has changed since 7.3, but the code behavior
is still fundamentally the same.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alfranio Correia Junior | 2006-01-21 01:54:44 | strange behavior on locks |
| Previous Message | Tom Lane | 2006-01-21 01:02:35 | Re: panic on 7.3 |