streaming replication and wraparound vacuuming

From: Andrew Shved <andys(at)aggregateknowledge(dot)com>
To: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: streaming replication and wraparound vacuuming
Date: 2011-09-30 19:28:15
Message-ID: 0370E60157CA7E4097D81B9E09728A9409A8701B31@MAILR001.mail.lan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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.

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Julius Tuskenis 2011-10-03 16:50:07 commiting transaction from outside
Previous Message Joe Conway 2011-09-29 17:29:41 Re: diagnosing a db crash - server exit code 2