pg_standby doesnt't work

--_000_158182AF0720CA4FBB0E7DC47600D5A81F397C0Bwinxbede14exc ha_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

I'm testing serveral days a replication-system with PostgreSQL, but I get a=
llways the same error.

2009-10-25 15:44:45 CET FATAL: XX000: could not restore file "00000001.his=
tory" from archive: return code -1073741811

The restore_command is:

restore_command =3D '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 dif=
ference 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 s=
o my archive_command can't replicate to the slave.

This is all content of 'backup_label' out of my base-backup:
START WAL LOCATION: 0/AE000020 (file 0000000100000000000000AE)
CHECKPOINT LOCATION: 0/AE000020
START TIME: 2009-10-25 14:36:25 CET
LABEL: 25102009_1

I can't get information out of pg_standby.log, there is nothing in.

That's the complete pg-log (debug-level 5):
2009-10-25 15:44:45 CET DEBUG: 00000: forked new backend, pid=3D1220 socke=
t=3D1312
2009-10-25 15:44:45 CET LOCATION: BackendStartup, .\src\backend\postmaster=
\postmaster.c:2861
2009-10-25 15:44:45 CET LOG: 00000: database system was interrupted; last =
known up at 2009-10-25 14:36:25 CET
2009-10-25 15:44:45 CET LOCATION: StartupXLOG, .\src\backend\access\transa=
m\xlog.c:4839
2009-10-25 15:44:45 CET LOG: 00000: starting archive recovery
2009-10-25 15:44:45 CET LOCATION: readRecoveryCommandFile, .\src\backend\a=
ccess\transam\xlog.c:4377
2009-10-25 15:44:45 CET LOG: 00000: restore_command =3D 'pg_standby.exe -d=
-s 5 -t C:\pgsql.trigger.5442 w:\wal-archive %f %p %r 2>>pg_log\pg_standby=
..log'
2009-10-25 15:44:45 CET LOCATION: readRecoveryCommandFile, .\src\backend\a=
ccess\transam\xlog.c:4423
2009-10-25 15:44:45 CET DEBUG: 00000: executing restore command "pg_standb=
y.exe -d -s 5 -t C:\pgsql.trigger.5442 w:\wal-archive 00000001.history pg_x=
log\RECOVERYHISTORY 000000000000000000000000 2>>pg_log\pg_standby.log"
2009-10-25 15:44:45 CET LOCATION: RestoreArchivedFile, .\src\backend\acces=
s\transam\xlog.c:2569
2009-10-25 15:44:45 CET LOG: 00000: loaded library "$libdir/plugins/plugin=
_debugger.dll"
2009-10-25 15:44:45 CET LOCATION: load_libraries, .\src\backend\utils\init=
\miscinit.c:1187
2009-10-25 15:44:45 CET FATAL: 57P03: the database system is starting up
2009-10-25 15:44:45 CET LOCATION: ProcessStartupPacket, .\src\backend\post=
master\postmaster.c:1648
2009-10-25 15:44:45 CET DEBUG: 00000: proc_exit(1)
2009-10-25 15:44:45 CET LOCATION: proc_exit, .\src\backend\storage\ipc\ipc=
..c:98
2009-10-25 15:44:45 CET DEBUG: 00000: shmem_exit(1)
2009-10-25 15:44:45 CET LOCATION: shmem_exit, .\src\backend\storage\ipc\ip=
c.c:164
2009-10-25 15:44:45 CET DEBUG: 00000: exit(1)
2009-10-25 15:44:45 CET LOCATION: proc_exit, .\src\backend\storage\ipc\ipc=
..c:116
2009-10-25 15:44:45 CET DEBUG: 00000: reaping dead processes
2009-10-25 15:44:45 CET LOCATION: reaper, .\src\backend\postmaster\postmas=
ter.c:2093
2009-10-25 15:44:45 CET DEBUG: 00000: server process (PID 1220) exited wit=
h exit code 1
2009-10-25 15:44:45 CET LOCATION: LogChildExit, .\src\backend\postmaster\p=
ostmaster.c:2520
2009-10-25 15:44:45 CET FATAL: XX000: could not restore file "00000001.his=
tory" from archive: return code -1073741811
2009-10-25 15:44:45 CET LOCATION: RestoreArchivedFile, .\src\backend\acces=
s\transam\xlog.c:2639
2009-10-25 15:44:45 CET DEBUG: 00000: proc_exit(1)
2009-10-25 15:44:45 CET LOCATION: proc_exit, .\src\backend\storage\ipc\ipc=
..c:98
2009-10-25 15:44:45 CET DEBUG: 00000: shmem_exit(1)
2009-10-25 15:44:45 CET LOCATION: shmem_exit, .\src\backend\storage\ipc\ip=
c.c:164
2009-10-25 15:44:45 CET DEBUG: 00000: exit(1)
2009-10-25 15:44:45 CET LOCATION: proc_exit, .\src\backend\storage\ipc\ipc=
..c:116
2009-10-25 15:44:45 CET DEBUG: 00000: reaping dead processes
2009-10-25 15:44:45 CET LOCATION: reaper, .\src\backend\postmaster\postmas=
ter.c:2093
2009-10-25 15:44:45 CET LOG: 00000: startup process (PID 3820) exited with=
exit code 1
2009-10-25 15:44:45 CET LOCATION: LogChildExit, .\src\backend\postmaster\p=
ostmaster.c:2520
2009-10-25 15:44:45 CET LOG: 00000: aborting startup due to startup proces=
s failure
2009-10-25 15:44:45 CET LOCATION: reaper, .\src\backend\postmaster\postmas=
ter.c:2113
2009-10-25 15:44:45 CET DEBUG: 00000: proc_exit(1)
2009-10-25 15:44:45 CET LOCATION: proc_exit, .\src\backend\storage\ipc\ipc=
..c:98
2009-10-25 15:44:45 CET DEBUG: 00000: shmem_exit(1)
2009-10-25 15:44:45 CET LOCATION: shmem_exit, .\src\backend\storage\ipc\ip=
c.c:164
2009-10-25 15:44:45 CET DEBUG: 00000: exit(1)
2009-10-25 15:44:45 CET LOCATION: proc_exit, .\src\backend\storage\ipc\ipc=
..c:116
2009-10-25 15:44:46 CET DEBUG: 00000: logger shutting down
2009-10-25 15:44:46 CET LOCATION: SysLoggerMain, .\src\backend\postmaster\=
syslogger.c:435
2009-10-25 15:44:46 CET DEBUG: 00000: proc_exit(0)
2009-10-25 15:44:46 CET LOCATION: proc_exit, .\src\backend\storage\ipc\ipc=
..c:98
2009-10-25 15:44:46 CET DEBUG: 00000: shmem_exit(0)
2009-10-25 15:44:46 CET LOCATION: shmem_exit, .\src\backend\storage\ipc\ip=
c.c:164
2009-10-25 15:44:46 CET DEBUG: 00000: exit(0)
2009-10-25 15:44:46 CET LOCATION: proc_exit, .\src\backend\storage\ipc\ipc=
..c:116

thx a lot,

murphy

--_000_158182AF0720CA4FBB0E7DC47600D5A81F397C0Bwinxbede14exc ha_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
[at] font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
[at] font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.E-MailFormatvorlage18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
..MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
[at] page Section1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>

<body lang=3DDE link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif";
color:black'>Hi,</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal> <o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif"'>I'm
testing serveral days a replication-system with PostgreSQL, but I get allwa=
ys
the same error.</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal> <o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif";
color:black'>2009-10-25 15:44:45 CET FATAL:  XX000: could not restore =
file
"00000001.history" from archive: return code -1073741811</span><o=
:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal> <o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif"'>The
restore_command is:</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal> <o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif"'>restore_command
=3D 'pg_standby.exe -d -s 5 -t C:\pgsql.trigger.5442 w:\wal-archive %f %p %=
r
2>>pg_log\pg_standby.log'</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal> <o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif"'>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 differenc=
e in
the result.</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal> <o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif"'>So
I can't understand what this return-code means, (and) I've never seen a fil=
e
named 00000001.history. It definitely doesn't exist on my master and so my
archive_command can't replicate to the slave.</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal> <o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif"'>This
is all content of 'backup_label' out of my base-backup:</span><o:p></o:p></=
p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif"'>START
WAL LOCATION: 0/AE000020 (file 0000000100000000000000AE)<br>
CHECKPOINT LOCATION: 0/AE000020<br>
START TIME: 2009-10-25 14:36:25 CET<br>
LABEL: 25102009_1</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal> <o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif"'>I
can't get information out of pg_standby.log, there is nothing in.</span><o:=
p></o:p></p>

</div>

<div>

<p class=3DMsoNormal> <o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif"'>That's
the complete pg-log (debug-level 5):</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif"'>2009-10-25
15:44:45 CET DEBUG:  00000: forked new backend, pid=3D1220 socket=3D13=
12<br>
2009-10-25 15:44:45 CET LOCATION:  BackendStartup,
..\src\backend\postmaster\postmaster.c:2861<br>
2009-10-25 15:44:45 CET LOG:  00000: database system was interrupted; =
last
known up at 2009-10-25 14:36:25 CET<br>
2009-10-25 15:44:45 CET LOCATION:  StartupXLOG,
..\src\backend\access\transam\xlog.c:4839<br>
2009-10-25 15:44:45 CET LOG:  00000: starting archive recovery<br>
2009-10-25 15:44:45 CET LOCATION:  readRecoveryCommandFile,
..\src\backend\access\transam\xlog.c:4377<br>
2009-10-25 15:44:45 CET LOG:  00000: restore_command =3D 'pg_standby.e=
xe -d
-s 5 -t C:\pgsql.trigger.5442 w:\wal-archive %f %p %r
2>>pg_log\pg_standby.log'<br>
2009-10-25 15:44:45 CET LOCATION:  readRecoveryCommandFile,
..\src\backend\access\transam\xlog.c:4423<br>
2009-10-25 15:44:45 CET DEBUG:  00000: executing restore command
"pg_standby.exe -d -s 5 -t C:\pgsql.trigger.5442 w:\wal-archive
00000001.history pg_xlog\RECOVERYHISTORY 000000000000000000000000
2>>pg_log\pg_standby.log"<br>
2009-10-25 15:44:45 CET LOCATION:  RestoreArchivedFile,
..\src\backend\access\transam\xlog.c:2569<br>
2009-10-25 15:44:45 CET LOG:  00000: loaded library
"$libdir/plugins/plugin_debugger.dll"<br>
2009-10-25 15:44:45 CET LOCATION:  load_libraries,
..\src\backend\utils\init\miscinit.c:1187<br>
2009-10-25 15:44:45 CET FATAL:  57P03: the database system is starting=
up<br>
2009-10-25 15:44:45 CET LOCATION:  ProcessStartupPacket,
..\src\backend\postmaster\postmaster.c:1648<br>
2009-10-25 15:44:45 CET DEBUG:  00000: proc_exit(1)<br>
2009-10-25 15:44:45 CET LOCATION:  proc_exit,
..\src\backend\storage\ipc\ipc.c:98<br>
2009-10-25 15:44:45 CET DEBUG:  00000: shmem_exit(1)<br>
2009-10-25 15:44:45 CET LOCATION:  shmem_exit,
..\src\backend\storage\ipc\ipc.c:164<br>
2009-10-25 15:44:45 CET DEBUG:  00000: exit(1)<br>
2009-10-25 15:44:45 CET LOCATION:  proc_exit,
..\src\backend\storage\ipc\ipc.c:116<br>
2009-10-25 15:44:45 CET DEBUG:  00000: reaping dead processes<br>
2009-10-25 15:44:45 CET LOCATION:  reaper, .\src\backend\postmaster\po=
stmaster.c:2093<br>
2009-10-25 15:44:45 CET DEBUG:  00000: server process (PID 1220) exite=
d
with exit code 1<br>
2009-10-25 15:44:45 CET LOCATION:  LogChildExit,
..\src\backend\postmaster\postmaster.c:2520<br>
2009-10-25 15:44:45 CET FATAL:  XX000: could not restore file
"00000001.history" from archive: return code -1073741811<br>
2009-10-25 15:44:45 CET LOCATION:  RestoreArchivedFile,
..\src\backend\access\transam\xlog.c:2639<br>
2009-10-25 15:44:45 CET DEBUG:  00000: proc_exit(1)<br>
2009-10-25 15:44:45 CET LOCATION:  proc_exit,
..\src\backend\storage\ipc\ipc.c:98<br>
2009-10-25 15:44:45 CET DEBUG:  00000: shmem_exit(1)<br>
2009-10-25 15:44:45 CET LOCATION:  shmem_exit,
..\src\backend\storage\ipc\ipc.c:164<br>
2009-10-25 15:44:45 CET DEBUG:  00000: exit(1)<br>
2009-10-25 15:44:45 CET LOCATION:  proc_exit,
..\src\backend\storage\ipc\ipc.c:116<br>
2009-10-25 15:44:45 CET DEBUG:  00000: reaping dead processes<br>
2009-10-25 15:44:45 CET LOCATION:  reaper,
..\src\backend\postmaster\postmaster.c:2093<br>
2009-10-25 15:44:45 CET LOG:  00000: startup process (PID 3820) exited
with exit code 1<br>
2009-10-25 15:44:45 CET LOCATION:  LogChildExit,
..\src\backend\postmaster\postmaster.c:2520<br>
2009-10-25 15:44:45 CET LOG:  00000: aborting startup due to startup
process failure<br>
2009-10-25 15:44:45 CET LOCATION:  reaper, .\src\backend\postmaster\po=
stmaster.c:2113<br>
2009-10-25 15:44:45 CET DEBUG:  00000: proc_exit(1)<br>
2009-10-25 15:44:45 CET LOCATION:  proc_exit,
..\src\backend\storage\ipc\ipc.c:98<br>
2009-10-25 15:44:45 CET DEBUG:  00000: shmem_exit(1)<br>
2009-10-25 15:44:45 CET LOCATION:  shmem_exit,
..\src\backend\storage\ipc\ipc.c:164<br>
2009-10-25 15:44:45 CET DEBUG:  00000: exit(1)<br>
2009-10-25 15:44:45 CET LOCATION:  proc_exit,
..\src\backend\storage\ipc\ipc.c:116<br>
2009-10-25 15:44:46 CET DEBUG:  00000: logger shutting down<br>
2009-10-25 15:44:46 CET LOCATION:  SysLoggerMain,
..\src\backend\postmaster\syslogger.c:435<br>
2009-10-25 15:44:46 CET DEBUG:  00000: proc_exit(0)<br>
2009-10-25 15:44:46 CET LOCATION:  proc_exit,
..\src\backend\storage\ipc\ipc.c:98<br>
2009-10-25 15:44:46 CET DEBUG:  00000: shmem_exit(0)<br>
2009-10-25 15:44:46 CET LOCATION:  shmem_exit,
..\src\backend\storage\ipc\ipc.c:164<br>
2009-10-25 15:44:46 CET DEBUG:  00000: exit(0)<br>
2009-10-25 15:44:46 CET LOCATION:  proc_exit,
..\src\backend\storage\ipc\ipc.c:116</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal> <o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif"'>thx
a lot,</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal> <o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif"'>murphy</span><o:p></o:p></p>

</div>

</div>

</body>

</html>

--_000_158182AF0720CA4FBB0E7DC47600D5A81F397C0Bwinxbede14exc ha_--
Andreas Schmidt [ So, 25 Oktober 2009 16:34 ] [ ID #2020335 ]

Re: [ADMIN] pg_standby doesnt't work

Hi,

On Mon, Oct 26, 2009 at 12:34 AM, Andreas Schmidt <a.schmidt [at] mdtec.de> wrot=
e:
> 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:=A0 XX000: could not restore file
> "00000001.history" from archive: return code -1073741811
>
> The restore_command is:
>
> restore_command =3D '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.
http://archives.postgresql.org/pgsql-bugs/2009-08/msg00003.p hp

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

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

--
Sent via pgsql-hackers mailing list (pgsql-hackers [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Fujii Masao [ Mo, 26 Oktober 2009 03:35 ] [ ID #2020415 ]

Re: [ADMIN] pg_standby doesnt't work

Hi, thank you for your response.
But does this mean, that only WinXP is no supported or doesn't it work at a=
ll? I would need it on a Windows2003Server???

Best regards,

murphy


-----Ursprüngliche Nachricht-----
Von: Fujii Masao [mailto:masao.fujii [at] gmail.com]
Gesendet: Montag, 26. Oktober 2009 03:36
An: Andreas Schmidt
Cc: pgsql-admin [at] postgresql.org; PostgreSQL-development
Betreff: Re: [ADMIN] pg_standby doesnt't work

Hi,

On Mon, Oct 26, 2009 at 12:34 AM, Andreas Schmidt <a.schmidt [at] mdtec.de> wrot=
e:
> 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:=A0 XX000: could not restore file
> "00000001.history" from archive: return code -1073741811
>
> The restore_command is:
>
> restore_command =3D '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.
http://archives.postgresql.org/pgsql-bugs/2009-08/msg00003.p hp

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

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

--
Sent via pgsql-hackers mailing list (pgsql-hackers [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Andreas Schmidt [ Di, 27 Oktober 2009 08:53 ] [ ID #2020565 ]

Re: [HACKERS] pg_standby doesnt't work

Hi,

On Tue, Oct 27, 2009 at 4:53 PM, Andreas Schmidt <a.schmidt [at] mdtec.de> wrote:
> Hi, thank you for your response.
> But does this mean, that only WinXP is no supported or doesn't it work at all? I would need it on a Windows2003Server???

According to the previous post, pg_standby in v8.3.7 would work file.
How about using that?
http://archives.postgresql.org/pgsql-bugs/2009-08/msg00094.p hp

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

--
Sent via pgsql-admin mailing list (pgsql-admin [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Fujii Masao [ Mi, 28 Oktober 2009 02:37 ] [ ID #2020760 ]

Re: [HACKERS] pg_standby doesnt't work

Hi,

On Tue, Oct 27, 2009 at 4:53 PM, Andreas Schmidt <a.schmidt [at] mdtec.de> wrote:
> Hi, thank you for your response.
> But does this mean, that only WinXP is no supported or doesn't it work at all? I would need it on a Windows2003Server???

This problem will disappear in the next release (v8.3.9, v8.4.2).
http://archives.postgresql.org/pgsql-committers/2009-11/msg0 0019.php

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

--
Sent via pgsql-admin mailing list (pgsql-admin [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Fujii Masao [ Do, 05 November 2009 05:19 ] [ ID #2021760 ]
Datenbanken » gmane.comp.db.postgresql.admin » pg_standby doesnt't work

Vorheriges Thema: installation problem
Nächstes Thema: pg_autovacuum entries