From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: odd output in restore mode |
Date: | 2008-05-13 03:03:25 |
Message-ID: | 482904FD.4030006@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>> Simon Riggs wrote:
>>
>>> Well, the patch was rejected long ago, not sure why its in this
>>> commitfest. But its an open issue on the Windows port.
>>>
>
>
>> Surely the right fix is to use the recently implemented
>> pgwin32_safestat() (if we aren't already - I suspect we probably are)
>> and remove the kluge in pg_standby.c.
>>
>
> I think the open issue is how to know whether pgwin32_safestat fixes the
> problem that the kluge tried to work around.
>
>
>
Well, I think we need to consider quite a number of scenarios. The
archive directory could be local, on a remote Windows machine, or on a
remote Samba server. The archive file could be copied by Windows copy,
or Unix cp, or scp, or rsync, among others.
I'd like to know the setup that was found to produce the error, to start
with.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2008-05-13 03:53:57 | Re: Syntax decisions for pl/pgsql RAISE extension |
Previous Message | Tom Lane | 2008-05-13 02:41:11 | Re: Syntax decisions for pl/pgsql RAISE extension |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2008-05-13 05:37:24 | Re: odd output in restore mode |
Previous Message | Andrew Dunstan | 2008-05-13 02:40:38 | Re: odd output in restore mode |