From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: 7.0.3 database corruption |
Date: | 2001-06-14 14:01:15 |
Message-ID: | 17370.992527275@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> mlw wrote:
>> After we run the
>> scripts, it looks like the database is corrupt.
It's impossible to say anything useful with such an undescriptive
description of the problem.
Hannu Krosing <hannu(at)tm(dot)ee> writes:
> There certainly are bugs in 7.0.3 - I can describe at least two:
I would really like to see a reproducible example of index corruption
in 7.0.*. We've heard such reports often enough to know the problem
is real, but without a test case in hand it's difficult to do much about
it.
> 2. Some kind of stuck locks - a single backend stuck in "INSERT waiting"
7.0.*'s deadlock detection algorithm is known to have some holes, but
deadlock couldn't be the explanation for just a single stuck backend.
Again, any chance of looking at an example?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David D. Kilzer | 2001-06-14 14:31:06 | [PATCH] Contrib C source for casting MONEY to INT[248] and FLOAT[48] |
Previous Message | Thomas Lockhart | 2001-06-14 13:54:59 | Re: Australian timezone configure option |