> > > > my company has been using pg_standby as a replication solution for a > > while and it has been working great for our needs. Unfortunately, about > > once a month we get the following error on the standby bases: > > > > vacuumdb: vacuuming of database "xxxx" failed: ERROR: could not access > > status of transaction 3625953267 > > DETAIL: Could not open file "pg_clog/0D81": No such file or directory. > > Is vacuum running on the standby? It's been a long day here, but I'm not > sure that makes sense. > You cannot vacuum the warm standby in PG 8.2. -- Patryk Sidzina -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
