Re: [GENERAL] NOTIFY command impact

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: [GENERAL] NOTIFY command impact
Дата
Msg-id CAKFQuwaGuMhUWoAnKU+0=QuaeHv5hQuyGtgPxVVb4HbkTnaYwg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [GENERAL] NOTIFY command impact  (Rob Brucks <rob.brucks@rackspace.com>)
Ответы Re: [GENERAL] NOTIFY command impact  (Benoit Lobréau <benoit.lobreau@gmail.com>)
Список pgsql-general
Дерево обсуждения
On Wed, Feb 22, 2017 at 3:05 PM, Rob Brucks <rob.brucks@rackspace.com> wrote:
So, long-term, you don't see any negative impacts to the master cluster?

I just don't want to implement this as a streaming "push" mechanism and then have my cluster crash in 12 months because it hit some obscure problem with notifications.

​The only concern related to "xid/transactions" that I can think of is:

​https://www.postgresql.org/docs/current/static/routine-vacuuming.html

"To avoid this, it is necessary to vacuum every table in every database at least once every two billion transactions."

Probably not appreciably but you will hit the 2B mark more quickly if you are burning off transaction ids in this manner.

David J.

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

Предыдущее
От: Dylan Luong
Дата:
Сообщение: [GENERAL] Postgres HA
Следующее
От: Jeff Janes
Дата:
Сообщение: Re: [GENERAL] Autovacuum stuck for hours, blocking queries