streaming replication and wraparound vacuuming

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

 



I have a set up where most of the data located in partitions of the large table and that data never changes.  The only table that really changes is current day's partition.  The problem is that transaction wraparound vacuum generates a lot of traffic quite frequently on partitions that never changed (technically read only).  This is especially a problem with streaming replication due to enormous amounts of logging activity that is being generated.  Is there a way to limit or eliminate those frequent vacuum. Something akin to oralce read only tablespace or a way to set frozen transaction xid on a partition level?  Basically anything to make it less frequent especially when there is zero activity on those tables after initial loads.


[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