-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello:
I've been writing a billing system with C++, ODBC, and PostgreSQL 7.1.2. After I optimized my queries, I was surprised at how fast PostgreSQL can swoop through 200,000 billing records. But I noticed, sometimes, the final stage of my processing never completes, and PostgreSQL is spiralling the CPU at almost 100%. I have to kill the process, which is thankfully detected by my application which does a rollback. Anyway, I'm quite sure it isn't my software that is causing this, because if I do a simple vacuum after the rollback, and then run the same sequence again, the final stage completes as quickly as I've come to expect. I'm just wondering if there is a known race condition or something else which would cause this phenomenon. Thanks in advance. - ---------------< LINUX: The choice of a GNU generation. >------------- Steve Frampton <[EMAIL PROTECTED]> http://www.LinuxNinja.com GNU Privacy Guard ID: D055EBC5 (see http://www.gnupg.org for details) GNU-PG Fingerprint: EEFB F03D 29B6 07E8 AF73 EF6A 9A72 F1F5 D055 EBC5 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.0 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7uvUJmnLx9dBV68URAoz5AJ4jIyNXAM1ly4iehXKczXEEtd1FNwCeLVEY SKJ4PPoMK7w2WlfmoWj+rnk= =fVJo -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
