streaming replication and wraparound vacuuming

Поиск
Список
Период
Сортировка
От Andrew Shved
Тема streaming replication and wraparound vacuuming
Дата
Msg-id 0370E60157CA7E4097D81B9E09728A9409A8701B31@MAILR001.mail.lan
обсуждение исходный текст
Ответы Re: streaming replication and wraparound vacuuming  (Greg Smith <greg@2ndQuadrant.com>)
Список 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.

В списке pgsql-admin по дате отправления:

Предыдущее
От: Joe Conway
Дата:
Сообщение: Re: diagnosing a db crash - server exit code 2
Следующее
От: "Burgholzer, Robert (DEQ)"
Дата:
Сообщение: Re: diagnosing a db crash - server exit code 2