Search Postgresql Archives

Re: NOTIFY command impact

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Feb 22, 2017 at 3:05 PM, Rob Brucks <rob.brucks@xxxxxxxxxxxxx> 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:


"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.


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux