Re: Something smells in this schema...
Adam Haberlach <adam@newsnipple.com>
From: Adam Haberlach <adam@newsnipple.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Adam Haberlach <adam@newsnipple.com>, pgsql-hackers@postgresql.org
Date: 2001-02-16T18:14:34Z
Lists: pgsql-hackers
On Fri, Feb 16, 2001 at 01:02:24PM -0500, Tom Lane wrote: > Adam Haberlach <adam@newsnipple.com> writes: > > I had postgres start blocking all it's UPDATEs on a production > > database today, when an engineer added the following two tables, > > among other things. We've had to restore from backup, and the > > interesting thing is that when we re-add these tables, things > > break again. > > "blocking"? Please define symptoms more precisely. The postgres process stalls. According to ps, it's it is attempting an UPDATE. I think it times out eventually (I was in disaster-recovery mode this morning, and not always waiting around for these things. :) > > My first thought was the index on the boolean field in the time_cards, > > which I could have sworn has caused me problems before. Anyone else see > > anything wrong? > > Pre-7.1 versions do have problems with large numbers of equal keys in > a btree index, which is more or less the definition of an index on > boolean. I'm dubious that such an index is of any value anyway ... Ok--I'll check this. Thanks for the incredibly fast response--my favorite thing about PostgreSQL is the fact that I can post to a mailing list and get clued answers from real developers, usually within hours if not minutes. -- Adam Haberlach |A cat spends her life conflicted between a adam@newsnipple.com |deep, passionate, and profound desire for http://www.newsnipple.com |fish and an equally deep, passionate, and '88 EX500 '00 >^< |profound desire to avoid getting wet.