Chris Browne wrote:
> [EMAIL PROTECTED] (Bruce Momjian) writes:
> > With no new additions submitted today, I have moved my text into our
> > SGML documentation:
> >
> > http://momjian.us/main/writings/pgsql/sgml/failover.html
> >
> > Please let me know what additional changes are needed.
>
> I
On Tue, 14 Nov 2006, Bruce Momjian wrote:
Your description was too detailed, but I took some of your concepts:
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. Hea
Jeff Frost wrote:
> On Tue, 14 Nov 2006, Bruce Momjian wrote:
>
> > Your description was too detailed, but I took some of your concepts:
> >
> >
> > In clustering, each server can accept write requests, and these
> > write requests are broadcast from the original server to all
> > other se
On Tue, 14 Nov 2006, Bruce Momjian wrote:
Jeff Frost wrote:
On Tue, 14 Nov 2006, Bruce Momjian wrote:
Your description was too detailed, but I took some of your concepts:
In clustering, each server can accept write requests, and these
write requests are broadcast from the original serv
Jeff Frost wrote:
> >>>
> >>> Clustering is implemented by Oracle in their
> >>> RAC product. PostgreSQL
> >>> does not offer this type of load balancing, though
> >>> PostgreSQL two-phase commit ( >>> linkend="sql-prepare-transaction-title"> and >>> "sql-commit-prepared-title">) ca
On Tue, 14 Nov 2006, Bruce Momjian wrote:
We had a long discussion about that and felt that recommending
commercial products or even every open source project was too much. The
idea was that we should reference a web page that has them all mentioned,
but no one has set one up yet.
That makes
Jeff Frost wrote:
> > FYI, as far as I know, Continuent's solution is "Query Broadcast Load
> > Balancing", not clustering.
>
> I would speculate that your terminology is slightly more accurate than mine.
> The do query broadcast, but they also do a bit more with it than that as they
> evaluate
On Tue, 14 Nov 2006, Bruce Momjian wrote:
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.
I guess it's kind of a fine line how it gets defined?
Hmmm. Interesting. Does
Jeff Frost wrote:
> On Tue, 14 Nov 2006, Bruce Momjian wrote:
>
> >> 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.
> >>
> >> I guess it's kind of a fine lin
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 t
Jeff Frost wrote:
> 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
On Tue, 14 Nov 2006, Bruce Momjian wrote:
"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.
Basically,
Jeff Frost wrote:
> On Tue, 14 Nov 2006, Bruce Momjian wrote:
>
> >> "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
13 matches
Mail list logo
