Here is my ugly work-around:
I had a midnight script that would import shut down webware, start up another instance of webware that would put up a 'System undergoing update, back in xxxminutes',
then it would drop the indexes, import 250k records, delete 250k records, rebuild indexes and vaccum static.
after that it would restart webware.
The app NEEDS indexes to work and the import took much too w/ indexes so this was the only approach to get it up the next day.
I think the Postgres docs suggest that COPY (COPY FROM?) is the proper way to do these imports, because they don't update indexes -- I think there may be some other optimizations for delete as well. I don't remember the details, but I'm sure the Postgres docs say more.
-- Ian Bicking | [EMAIL PROTECTED] | http://blog.ianbicking.org
------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
