[Babase] Queries that run forever

Karl O. Pinc kop at meme.com
Wed Apr 4 00:50:35 EDT 2007


On 04/03/2007 11:43:25 PM, Tyler Brock wrote:
> ok awesome yes it looks like rnktypes is in order now, I'm looking  
> into why the insert doesn't work but they all used to work fine as I  
> had said, I have no idea why this would change, here is another  
> example:
> 
> INSERT INTO ranks VALUES (nextval('ranks_rnkid_seq'::regclass),  
> 'ALI', '1984-1-01', '1.0', 'ADF', '1');

(and for extra syntaxy goodness don't quote data going into
any sort of numeric column)

> 
> Please let me know if you find anything or if you have any ideas, its  
> a pretty simple update of one tuple, it shouldn't take too long. I  
> just tried to do do an explain analyze on that query and it doesn't  
> work either, it just sits there.

My triggers are doing something.  The question is, what?

The first thing I'm doing is a "vacuum analyze" on
the entire babase_copy database.  I don't have automatic
vacuuming turned on because it interfers with the
conversion but unless the database is analyzed the
query plans can be mis-optimized.  Maybe the data's
changed since I loaded it.  (BTW, you need to
reconnect to get new query plans.  This would
be an issue with psql or your java app but not
ppa.)

Karl <kop at meme.com>
Free Software:  "You don't pay back, you pay forward."
                  -- Robert A. Heinlein



More information about the Babase mailing list