Note : I do not know your database size and WAL archive generation rate.
Important considerations i made were as follows -
1. WAL archives transfer from production to standy depends on the network bandwidth (i think you said there is no issue there) and the size of the
WAL archives.
2. Transfer rate can be optimized by compressing the WAL files. Each WAL file size would reduce to 2 - 3 MB from 16 MB (only in case of warm
standby. In streaming replication size would decrease to 7 or 6 MB), which makes huge difference for the network bandwidth.
Compress the WAL archives at the production and transfer & uncompress the WALs on standby.
I did this successfully.
Hope this helps !
Thanks
Venkat
On Tue, Sep 6, 2011 at 2:57 AM, MirrorX <mirrorx@xxxxxxxxx> wrote:
the nodes communicate through 4Gbps ethernet so i dont think there is an
issue there. probably some kind of misconfiguration of DRBD has occured. i
will check on that tommorow. thx a lot :)
--
View this message in context: http://postgresql.1045698.n5.nabble.com/warm-standby-apply-wal-archives-tp4770567p4772126.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
