Dennis Thrysøe wrote:
> After copying a new dump of the MASTER cluster data and starting
> the SLAVE with this data, I now get:
>
> Database cluster state: in production
> ..
> Minimum recovery ending location: 0/0
Somehow it completed archive recovery and switched over to
pr
On Fri, Apr 09, 2010 at 10:19:20AM +0200, Dennis Thrys?e wrote:
> "cp: cannot stat `/psql_archive/0001.history': No such file or directory"
>
> By the way, one of these lines each second!
>
> "2010-04-09 09:09:49 IST FATAL: the database system is starting up"
I asked about this a few weeks
Hi again,
After copying a new dump of the MASTER cluster data and starting the SLAVE with
this data, I now get:
Database cluster state: in production
..
Minimum recovery ending location: 0/0
Still not exactly as expected, I guess. The log says things like :
"cp: cannot stat `
Dennis Thrysøe wrote:
> 1) The master keeps writing WAL files even though I'm quite sure
> nothing is happening. This seems like a large waste of diskspace?
What is your setting for archive_timeout? This limits how long
before a WAL file is sent. You could extend the time, although that
means
Hi,
I have a few elaborating questions in regard to setting up Warm Standby.
1) The master keeps writing WAL files even though I'm quite sure nothing is
happening. This seems like a large waste of diskspace?
2) Sometimes my slave does not read and delete WAL files when in recovery mode.
This w
