> > 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
> http://old.nabble.com/control-the-number-of-clog-files-and-xlog-files
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
http://old.nabble.com/control-the-number-of-clog-files-and-xlog
> >
> > 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
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 "xx
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
