On Sun, Mar 7, 2010 at 6:06 PM, Markus Wollny <Markus.Wollny@xxxxxxxxxxx> wrote: > Hi! > > After going several months without such incidents, we now got bit by the same problem again. We have since upgraded the hardware we ran the database cluster on and currently use version 8.3.7. The general outline of the problem hasn't changed much though - we still don't use the database 'postgres' except for one lone pgagent-job which has only been configured a couple of weeks back and we do a nightly vacuum over all databases in addition the the running of the autovacuum daemon. As I expect that this might hit again in a couple of months: Any suggestions on what sort of forensic data might be required to actually find out the root of what's causing it? As I needed to get the cluster back up and running again, I used the same remedy as last time and simply dropped the database and recreated it from template1, so there's not much left to be looked into right now, but if I knew what kind of data to retain I mit be able to come up with some more useful info next time... Do your logs show any kind of error when vacuuming about "only owner can vacuum" a table or anything? -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
