actually, I'm using postgresql 7.3.2. I noticed there were some hash index fixes in 7.4, so that might be it. Would there be any other reason for this deadlock? This database has been in production for almost 2 years and this is the first time we've seen the problem. thanks, Eugene > > From: Alvaro Herrera <alvherre@xxxxxxxxxxxxxx> > Date: 2005/08/19 Fri AM 11:22:04 EST > To: Eugene <eugene1@xxxxxxxxxxxx> > CC: pgsql-general@xxxxxxxxxxxxxx > Subject: Re: total db lockup > > 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) > ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your message can get through to the mailing list cleanly
