Postgres Pro
Downloads
Home   >   mailing lists

Re: [GENERAL] NOTIFY command impact - Mailing list pgsql-general

From David G. Johnston
Subject Re: [GENERAL] NOTIFY command impact
Date
Msg-id CAKFQuwaGuMhUWoAnKU+0=QuaeHv5hQuyGtgPxVVb4HbkTnaYwg@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] NOTIFY command impact  (Rob Brucks <rob.brucks@rackspace.com>)
Responses Re: [GENERAL] NOTIFY command impact  (Benoit Lobréau <benoit.lobreau@gmail.com>)
List pgsql-general
Tree view
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 by date:

Previous
From: Dylan Luong
Date:
Subject: [GENERAL] Postgres HA
Next
From: Jeff Janes
Date:
Subject: Re: [GENERAL] Autovacuum stuck for hours, blocking queries