Path: csiph.com!x330-a1.tempe.blueboxinc.net!feeder1.hal-mli.net!nx02.iad01.newshosting.com!newshosting.com!news-out.readnews.com!transit3.readnews.com!news-out.news.tds.net!newsreading01.news.tds.net!86597e80!not-for-mail From: "Martin Gregorie" Subject: PostgresQL 55000 error Message-ID: X-Comment-To: comp.lang.java.databases Newsgroups: comp.lang.java.databases Content-Type: text/plain; charset=IBM437 Content-Transfer-Encoding: 8bit X-Gateway: time.synchro.net [Synchronet 3.15a-Win32 NewsLink 1.92] Lines: 38 Date: Wed, 27 Apr 2011 15:22:12 GMT NNTP-Posting-Host: 96.60.20.240 X-Complaints-To: news@tds.net X-Trace: newsreading01.news.tds.net 1303917732 96.60.20.240 (Wed, 27 Apr 2011 10:22:12 CDT) NNTP-Posting-Date: Wed, 27 Apr 2011 10:22:12 CDT Organization: TDS.net Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.databases:178 To: comp.lang.java.databases I've recently had a database I'm developing grind to a halt with error 55000, apparently connected to a "select nextval('softdbk');" statement I'm using to generate soft DBKs. These are integers - none have yet exceeded 5 figures (63195 on the production database, 10 on the test database). Neither database can currently be updated. I'm running Postgres 8.2.7 under Fedora 8, kernel 2.6.25.4-10.fc8. The application is using current JBDK drivers and was compiled and run under JDK 6.0_05. The application was running OK until 2-3 days ago, when it suddenly started throwing 55000 errors. The sequence select statement is being caught and reported by my exception trap, so its the obvious immediate culprit. I'd made minor changes to the application around this time, but nothing that should have affected database access at all: the class containing all database access methods for the affected program was not changed at all. I'm using a single sequence to generate soft DBKs for use as the prime keys of all tables. Before you ask, the natural keys are all long (80 characters or more), so soft DBKs save a lot of space and probably make joins faster. If you've seen Postgres 55000 errors I'd like to know the circumstances and how you resolved them as it might give me a clue about is causing this. There is nothing obvious in the logs. Recreating a test version of the database hasn't helped. The sequence select works OK from psql. -- martin@ | Martin Gregorie gregorie. | org | Zappa fan & glider pilot --- * Synchronet * The Whitehouse BBS --- whitehouse.hulds.com --- check it out free usenet! --- Synchronet 3.15a-Win32 NewsLink 1.92 Time Warp of the Future BBS - telnet://time.synchro.net:24