Greg, thanks for your answers. My comments below...
> From: gsst...@gmail.com [mailto:gsst...@gmail.com] On Behalf Of Greg Stark > Sent: Wednesday, August 04, 2010 9:35 PM > Firstly, the current release of 8.2 is 8.2.17. There are a long list of bugs > fixed in those intervening releases including one involving vacuum truncating > relations. I don't think it's the same problem but I would recommend updating > immediately to 8.2.17. > [HiteshB] I have noted your recommendation and will work with our Product Management to upgrade to the latest and greatest. Although we can't change the version that the customer has installed (8.2.9-1). > > > Secondly we don't recommend running VACUUM FULL routinely. It should only be > necessary in extraordinary circumstances. Normally a plain VACUUM (or VACUUM > ANALYZE or VACUUM VERBOSE) should be sufficient as long as it's being run > regularly. Regular VACUUM without the "FULL" > has much less impact on the system. > [HiteshB] Point noted. The decision to use VACUUM FULL is something we'll re-examine. Could you give an example of what an 'extraordinary circumstance' would be? > > "Permission denied" smells like a Windows problem with concurrent file > operations. Are you sure you're not running any anti-virus software or backup > software which could have these files open and prevent Postgres from > performing regular file operations on its files? Many people have reported > other problems with anti-virus software in particular. > [HiteshB] We have worked with the customer to exclude the postgre directory from their antivirus scans. Hopefully we won't see this Permission issue again. Thanks again. Regards, Hitesh -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
