Eric Kerin wrote:
> On Wed, 2004-08-11 at 16:43, Tom Lane wrote:
>
>>Gaetano Mendola <mendola@bigfoot.com> writes:
>>
>>>Tom Lane wrote:
>>>
>>>>It should work; dunno if anyone has tried it yet.
>>
>>>I was thinking about it but I soon realized that actually is
>>>impossible to do, postgres replay the log only if during the
>>>start the file recover.conf is present in $DATA directory :-(
>>
>><SNIP>
>>
>>Somebody should hack this together and try it during beta. I don't
>>have time myself.
>>
>> regards, tom lane
>
>
>
> I've wrote up a very quick, and insanely dirty hack to do log shipping.
> Actually, it's so poorly written I kinda feel ashamed to post the code.
>
> But so far the process looks very promising, with a few caveats.
>
> The issues I've seen are:
> 1. Knowing when the master has finished the file transfer transfer to
> the backup.
> 2. Handling the meta-files, (.history, .backup) (eg: not sleeping if
> they don't exist)
> 3. Keeping the backup from coming online before the replay has fully
> finished in the event of a failure to copy a file, or other strange
> errors (out of memory, etc).
I did the same work and I had the same problems solved in the exact way
you did, however my version was shell based ( wasted time ) :-(
I guess is better mantain the C version, I will take a look at it and
I will modify it if something doesn't work.
Good work.
Regards
Gaetano Mendola