Ariz Jacinto wrote:
Arizrunning transactions on postgres remotely can be really slow (no wonder they have an elephant for a logo) especially when you are accessing it thru ODBC (it's like an thai elephant carrying a log).
If you're doing many INSERT/UPDATE/DELETE statements, are you combining them in a single BEGIN/COMMIT (or ROLLBACK) transaction? If you don't explicitly BEGIN/COMMIT your transactions, PostgreSQL assumes one transaction per SQL statement. This makes a very big difference in performance.
Also, if you're just doing bulk INSERTs, you might want to use COPY instead.
Brian
--
"It's going to look pretty good, then, isn't it," said War testily, "the One
Horseman and Three Pedestrians of the Apocralypse."
-- The Four Horsemen of the Apocralypse encounter unexpected difficulties
(Terry Pratchett, Sourcery)
_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
Fully Searchable Archives With Friendly Web Interface at http://marc.free.net.ph
To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
