to wait untill 16 MB is filled.
One work around for this is setting your "archive_timeout" parameter to
lesser value or manualy switching the WAL archiving by command
"pg_switch_xlog"
Hope This will help
With Regards
Ashish
jasme <jassybaj@xxxxxxxxx> wrote:
hi,
i had made necessary change in the postgresql.conf for enabling WAL. How can
i know that WAL is working?
The configurations done in the postgresql.conf file is as below:
#---------------------------------------------------------------------------
# WRITE AHEAD LOG
#---------------------------------------------------------------------------
# - Settings -
fsync = true # turns forced synchronization on or off
wal_sync_method = fsync # the default varies across platforms:
# fsync, fdatasync, fsync_writethrough,
# open_sync, open_datasync
wal_buffers = 8 # min 4, 8KB each
commit_delay = 0 # range 0-100000, in microseconds
commit_siblings = 5 # range 1-1000
# - Checkpoints -
checkpoint_segments = 3 # in logfile segments, min 1, 16MB each
checkpoint_timeout = 300 # range 30-3600, in seconds
checkpoint_warning = 30 # 0 is off, in seconds
# - Archiving -
archive_command = 'cp -i %p /testpg/server/archivedir/%f
your response will be highly appreciated.
thanks
--
View this message in context: http://www.nabble.com/WAL-tf3685432.html#a10301494
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
Check out what you're missing if you're not on Yahoo! Messenger
