Search Postgresql Archives

synchronous replication: blocking commit on the master

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

I have observed that a commit on a replication master hangs if there are no slaves to communicate with if synchronous replication is enabled. I believe I have seen a posting that this behavior is deliberate.

In my environment I'd prefer to have the master continue processing transactions if there is a failure at the slave. Questions:
  • is there any way to allow the master proceed if the slave is unavailable (perhaps a configuration parameter I'm missing)?
  • if not, is there any ideological objection to allowing the master to continue for users that would prefer that behavior?

[Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Programming PHP]     [Kernel Newbies]     [PHP Classes]     [Find Someone Nice]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux