Re: [GENERAL] Missing clog, PITR

2010-02-25 Thread Patryk Sidzina
1) how do the clogs relate to wal shipping based replication? Clearly the master doesn't need that clog but the slave does. They should just be kept in sync. There's some useful background on this topic at

Re: [GENERAL] Missing clog, PITR

2010-02-24 Thread Greg Smith
Patryk Sidzina wrote: 1) how do the clogs relate to wal shipping based replication? Clearly the master doesn't need that clog but the slave does. They should just be kept in sync. There's some useful background on this topic at

[GENERAL] Missing clog, PITR

2010-02-22 Thread Patryk Sidzina
Hello everyone, 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 failed: ERROR: could not access status

Re: [GENERAL] Missing clog, PITR

2010-02-22 Thread Richard Huxton
On 22/02/10 09:57, Patryk Sidzina wrote: Hello everyone, 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

Re: [GENERAL] Missing clog, PITR

2010-02-22 Thread Patryk Sidzina
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 failed: ERROR: could not access status of