Re: [HACKERS] Replication documentation addition
От | Jeff Frost |
---|---|
Тема | Re: [HACKERS] Replication documentation addition |
Дата | |
Msg-id | Pine.LNX.4.64.0611141534330.23695@discord.home.frostconsultingllc.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] Replication documentation addition (Bruce Momjian <bruce@momjian.us>) |
Ответы |
Re: [HACKERS] Replication documentation addition
|
Список | pgsql-docs |
On Tue, 14 Nov 2006, Bruce Momjian wrote: >> My thinking on the definition of clustering was that there is some smarts for >> graceful failover and automated or semi-automated ways of bringing failed DB >> servers back up to date and online with the rest of the servers in the >> cluster. All servers need to be able to accept writes, but do we > > No, even replication servers can have that. > >> differentiate on where the writes originated (i.e. middleware or another >> postgresql server) or on functionality? > > Fundamentally, broadcast means the queries are being propogated outside > the server, with the benefits and limitations inherent in that. I'd definitely have to agree with you on that. I guess I'm trying to decide what differentiates clustering for load balancing from query broadcast based on your text. Maybe just don't use the word broadcast here: "In clustering, each server can accept write requests, and these write requests are broadcast from the original server to all other servers before each transaction commits." Unfortunately, I can't seem to come up with anything more clever. -- Jeff Frost, Owner <jeff@frostconsultingllc.com> Frost Consulting, LLC http://www.frostconsultingllc.com/ Phone: 650-780-7908 FAX: 650-649-1954
В списке pgsql-docs по дате отправления: