[ADMIN] Autovacuum seems to block database: WARNING worker took too long to start

Hi all, I'm having a strange problem with postgres & autovacuum Everything is working fine until I start getting the following errors ... and postgres stops working shortly after (it stops accepting connections) 2010-11-13 12:34:08.599 CET|1|||7104||4cde77b0.1bc0|2010-11-13 12:34:08 CET|1/44303|0

Re: [ADMIN] Autovacuum seems to block database: WARNING worker took too long to start

Hi Tom, thanks for your detailed responses. I really appreciate it. My comments below inline ... > > I'm having a strange problem with postgres & autovacuum > > Everything is working fine until I start getting the following errors ... > > and postgres stops working shortly after (it stops accepti

[ADMIN] Postgres error: could not open relation base/xxxxx/yyyyy

Hi all, We've been using postgres for 9 years without a problem until now! Two problems in a very short time! The first one is described in http://postgresql.1045698.n5.nabble.com/Autovacuum-seems-to-block-database-WARNING-worker-took-too-long-to-start-td3264261.html This is another one (not relat

Re: [ADMIN] Postgres error: could not open relation base/xxxxx/yyyyy

y upgrade) backups like expensive > chinese vases. > Start from those good and trustworthy backups to do any database "replay" > (or similar) work which > would lead to a viable situation. > > Στις Monday 15 November 2010 11:55:38 ο/η Pablo Delgado Díaz-Pache έγραψε: > &

Re: [ADMIN] Autovacuum seems to block database: WARNING worker took too long to start

Not sure what you mean. Once we start getting that error in the postgres log, there is no autovacuum entry. Only that error message once every minute (and as i wrote in my last email, the same message all the time). The question is what is causing postgres to stop working. Autovacuum or another r