| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Rob Brucks <rob(dot)brucks(at)rackspace(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, François Beaulieu <frank(at)tzone(dot)org>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: NOTIFY command impact |
| Date: | 2017-02-22 23:04:09 |
| Message-ID: | CAKFQuwaGuMhUWoAnKU+0=QuaeHv5hQuyGtgPxVVb4HbkTnaYwg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Feb 22, 2017 at 3:05 PM, Rob Brucks <rob(dot)brucks(at)rackspace(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2017-02-22 23:48:37 | Re: Autovacuum stuck for hours, blocking queries |
| Previous Message | Dylan Luong | 2017-02-22 22:58:10 | Postgres HA |