From: | Vlad Kosilov <vkosilov(at)contigo(dot)com> |
---|---|
To: | Ioannis Tambouras <ioannis(at)akroninc(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_standby stuck on a wal file size <16MB |
Date: | 2008-05-18 00:18:42 |
Message-ID: | 482F75E2.8080206@contigo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
is this wrong of me to expect that postgres would not make a wal file
available to archive_command unless it was completely ready to let go of
that wal file?
thanks,
V.
Ioannis Tambouras wrote:
>> archive_command = 'test ! -f /usr/local/wal_archive_local/%f && cp %p
>> /usr/local/wal_archive_local/%f'
>>
>
> The archive command tests if the wal segment exists and is a file,
> but it does not check if the file is still being written. You need to
> copy the file after writing has finished (it reached 16777216 bytes).
> I don't have sources of pg_standby near me, but I remember in the
> C code checks for complete segment sizes.
>
>
> thanks
> Ioannis Tambouras
>
>
>
--
________________________________________
Vladimir (Vlad) Kosilov
Senior Systems Administrator
Contigo Systems Inc.
604.683.3106 (phone)
604.648.9886 (fax)
vkosilov(at)contigo(dot)com
www.contigo.com
________________________________________
From | Date | Subject | |
---|---|---|---|
Next Message | Gurjeet Singh | 2008-05-18 02:39:46 | Re: pg_standby stuck on a wal file size <16MB |
Previous Message | Vlad Kosilov | 2008-05-18 00:11:21 | Re: pg_standby stuck on a wal file size <16MB |