Re: total db lockup

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Eugene <eugene1(at)sympatico(dot)ca>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: total db lockup
Date: 2005-08-19 15:22:04
Message-ID: 20050819152204.GH12685@surnet.cl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Aug 19, 2005 at 10:54:35AM -0400, Eugene wrote:
> Thanks Alvaro.
>
> Here it is again:
>
> problem description: http://rafb.net/paste/results/bLAtIk26.html
> db state before first restart: http://rafb.net/paste/results/D1Bqe125.html
> db state before second restart: http://rafb.net/paste/results/D1Bqe125.html
> table definition: http://rafb.net/paste/results/W35ccD49.html

Ok, so it seems the lockup occured only with the hash indexes? Then it
means we still have bugs in the locking code for those. It doesn't
surprise me. There's a reason they are not recommended, you know?

Let us know if you find the problem showing up again with btree indexes.
The hash indexes bugs should be fixed, but they are not high priority ...

--
Alvaro Herrera (<alvherre[a]alvh.no-ip.org>)
"If it wasn't for my companion, I believe I'd be having
the time of my life" (John Dunbar)

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adam Witney 2005-08-19 15:30:21 Re: http://www.postgresql.org/docs/8.0/static/xfunc-sql.html
Previous Message Adam Witney 2005-08-19 15:17:37 How to cancel a query if SIGINT does not work?