How to avoid generation huge pg_xlog files during VACUUM , REINDEX maintenance task.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi All,

We have a High transactional Database with Streamline Replication in place across two Data Centers with the dedicated leased line. The SR works awesome all time.

We do vacuum+reindex of few imp high transactional tables (not an entire database) which generates many pg_xlog files indeed creates Huge spike of Data transfer between two networks and burst the bandwidth only during this time.

Can we avoid the generating pg_xlog files for vacuum + reindex ?  Are any other solutions to it ?  Our vacuum + reindex is very very minimal and based on dead rows stats.

PG version :  9.0.4 ( on 64 bit OS).


Thanks,
Shrinivas Devarkonda.




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux