On Wed, May 21, 2008 at 4:14 AM, Vlad Kosilov <[EMAIL PROTECTED]> wrote:
> as Greg pointed out: my use of rsync --remove-sent-files option had
> contributed to a short sized wal log file on standby.
> changing master's postgres crontab to the following helped to resolve the
> issue:
>
> # ship log
as Greg pointed out: my use of rsync --remove-sent-files option had
contributed to a short sized wal log file on standby.
changing master's postgres crontab to the following helped to resolve
the issue:
# ship logs to standby:
*/2 * * * * rsync -aq /wal_archive_local/ 10.10.10.12::wal_archi
Greg, I think you might be onto something here. your suggestion prompts
to get rid off --remove-sent-files in my rsync command, and clean up wal
files from master by some other means, this way even if master's rsync
picks partial file on the first run, it should update and complete file
once it
On Sat, 17 May 2008, Ioannis Tambouras wrote:
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.
That's because it doesn't have to; the archive command doesn't get called
until the writing is done.
I don't have sourc
On Sun, May 18, 2008 at 5:48 AM, Vlad Kosilov <[EMAIL PROTECTED]> wrote:
> 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?
>
thats a perfectly reasonable expectation; and thats exactl
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_loca
Gurjeet Singh wrote:
archive_command = 'test ! -f /usr/local/wal_archive_local/%f && cp %p
/usr/local/wal_archive_local/%f'
archive files are then moved on master to standby every other minute:
rsync -aq --remove-sent-files /usr/local/wal_archive_local/
slave::wal_archive/
slave's recovery.co
> 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 re
On Sun, May 18, 2008 at 12:17 AM, Vladimir Kosilov <[EMAIL PROTECTED]>
wrote:
> I've been having problem with pgsql-8.2.5 master/slave warm standby
> replication setup where occasionally master node generates a wal file
> smaller then expected 16MB. pg_standby on slave gets stuck on such short
> f
I've been having problem with pgsql-8.2.5 master/slave warm standby
replication setup where occasionally master node generates a wal file
smaller then expected 16MB. pg_standby on slave gets stuck on such short
files, and replication halts from that moment on. we have to do
pg_start_backup/ rsy
10 matches
Mail list logo
