Skip site navigation (1) Skip section navigation (2)

Re: pg_standby doesnt't work

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Andreas Schmidt <a(dot)schmidt(at)mdtec(dot)de>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_standby doesnt't work
Date: 2009-10-26 02:35:59
Message-ID: (view raw or whole thread)
Lists: pgsql-adminpgsql-hackers

On Mon, Oct 26, 2009 at 12:34 AM, Andreas Schmidt <a(dot)schmidt(at)mdtec(dot)de> wrote:
> I'm testing serveral days a replication-system with PostgreSQL, but I get
> allways the same error.
> 2009-10-25 15:44:45 CET FATAL:  XX000: could not restore file
> "00000001.history" from archive: return code -1073741811
> The restore_command is:
> restore_command = 'pg_standby.exe -d -s 5 -t C:\pgsql.trigger.5442
> w:\wal-archive %f %p %r 2>>pg_log\pg_standby.log'
> The system is runnig on WinXP (during this test), the database-version is
> 8.3.8. I've tried out the pg_standby-version from PG8.4, but there is no
> difference in the result.
> So I can't understand what this return-code means, (and) I've never seen a
> file named 00000001.history. It definitely doesn't exist on my master and so
> my archive_command can't replicate to the slave.

This is the same problem that was reported before.

The cause is the signals support for pg_standby on win32.
We should get rid of that.


Fujii Masao
NTT Open Source Software Center

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2009-10-26 02:48:02
Subject: Re: License clarification: BSD vs MIT
Previous:From: Tom LaneDate: 2009-10-26 02:34:02
Subject: Endgame for all those SELECT FOR UPDATE changes: fix plan node order

pgsql-admin by date

Next:From: Steve CrawfordDate: 2009-10-26 04:41:56
Subject: Re: pg_attribute size
Previous:From: Andreas SchmidtDate: 2009-10-25 15:34:26
Subject: pg_standby doesnt't work

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group