Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> writes: > If the synchronicity is configured in the standby, how does the master know > that there's a synchronous slave out there that it should wait for, if that > slave isn't connected at the moment?
That's what quorum is trying to solve. The master knows how many votes per sync level the transaction needs. If no slave is acknowledging any vote, that's all you need to know to ROLLBACK (after the timeout), right? — if setup says so, on the master. > Yeah, the quorum stuff. That's all good, but doesn't change the way you > would do per-transaction control. That's when I bought in on the feature. It's all dynamic and distributed, and it offers per-transaction control. Regards, -- Dimitri Fontaine PostgreSQL DBA, Architecte -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
