Re: total db lockup - Mailing list pgsql-general

From Alvaro Herrera
Subject Re: total db lockup
Date
Msg-id 20050819152204.GH12685@surnet.cl
Whole thread Raw
In response to Re: total db lockup  (Eugene <eugene1@sympatico.ca>)
Responses Re: total db lockup
List 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)

pgsql-general by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: [BUGS] BUG #1830: Non-super-user must be able to copy
Next
From: Adam Witney
Date:
Subject: How to cancel a query if SIGINT does not work?