Hi,
Decibel! wrote:
But is the complete transaction information safely stored on all nodes
before a commit returns?
Good question. It depends very much on the group communication system
and the guarantees it provides for message delivery. For certain, the
information isn't safely stored on e
On Fri, Aug 24, 2007 at 06:54:35PM +0200, Markus Schiltknecht wrote:
> Gregory Stark wrote:
> >Only if your application is single-threaded. By single-threaded I don't
> >refer
> >to operating system threads but to the architecture. If you're processing a
> >large batch file handling records one by
Hello Bill,
Bill Moran wrote:
It appears as if I miscommunicated my point. I'm not expecting
PostgreSQL-R to break the laws of physics or anything, I'm just
curious how it reacts. This is the difference between software
that will be really great one day, and software that is great now.
Agree
In response to Markus Schiltknecht <[EMAIL PROTECTED]>:
> Hi,
>
> Bill Moran wrote:
> > I'm curious as to how Postgres-R would handle a situation where the
> > constant throughput exceeded the processing speed of one of the nodes.
>
> Well, what do you expect to happen? This case is easily detec
On 8/23/07, Decibel! <[EMAIL PROTECTED]> wrote:
> On Aug 22, 2007, at 3:37 PM, Joshua D. Drake wrote:
> > You can not do multi master cross continent reliably.
>
> I'm pretty sure that credit card processors and some other companies
> do it... it just costs a LOT to actually do it well.
And most c
Hi,
Marko Kreen wrote:
Such situation is not a specific problem to Postgres-R or to
synchronous replication in general. Asyncronous replication
will break down too.
Agreed, except that I don't consider slowness as 'breaking down'.
Regards
Markus
---(end of broadcast
On 8/26/07, Bill Moran <[EMAIL PROTECTED]> wrote:
> I'm curious as to how Postgres-R would handle a situation where the
> constant throughput exceeded the processing speed of one of the nodes.
Such situation is not a specific problem to Postgres-R or to
synchronous replication in general. Asyncro
Hi,
Bill Moran wrote:
I'm curious as to how Postgres-R would handle a situation where the
constant throughput exceeded the processing speed of one of the nodes.
Well, what do you expect to happen? This case is easily detectable, but
I can only see two possible solutions: either stop the node
Markus Schiltknecht <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Gregory Stark wrote:
> > Only if your application is single-threaded. By single-threaded I don't
> > refer
> > to operating system threads but to the architecture. If you're processing a
> > large batch file handling records one by one an
Hi,
Gregory Stark wrote:
Only if your application is single-threaded. By single-threaded I don't refer
to operating system threads but to the architecture. If you're processing a
large batch file handling records one by one and waiting for each commit
before proceeding then it's single threaded.
Hi,
Matthew wrote:
Hey all, new postgres user here. We are trying to setup/research an
HA/Replicated solution with Postrgresql between a datacenter in LA and a
d.c. in NY.
We have a private LAN link between the two D.C.'s with a max round-trip
of 150ms.
We will have a web server at each d.c. (
"Ron Johnson" <[EMAIL PROTECTED]> writes:
> On 08/24/07 08:21, Markus Schiltknecht wrote:
>
>> This is commonly known as synchronous replication. As that involves
>> *at-least* one round-trip *before* committing, it's quite expensive. Can
>> you live with a delay of ~150ms before COMMIT confirmati
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/24/07 08:21, Markus Schiltknecht wrote:
> Hi,
>
> Matthew wrote:
>> Hey all, new postgres user here. We are trying to setup/research an
>> HA/Replicated solution with Postrgresql between a datacenter in LA and a
>> d.c. in NY.
>>
>> We have a pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/23/07 17:22, Bill Moran wrote:
> Decibel! <[EMAIL PROTECTED]> wrote:
>> On Aug 22, 2007, at 3:37 PM, Joshua D. Drake wrote:
>>> You can not do multi master cross continent reliably.
>> I'm pretty sure that credit card processors and some other co
Decibel! <[EMAIL PROTECTED]> wrote:
>
> On Aug 22, 2007, at 3:37 PM, Joshua D. Drake wrote:
> > You can not do multi master cross continent reliably.
>
> I'm pretty sure that credit card processors and some other companies
> do it... it just costs a LOT to actually do it well.
Isn't this sort o
On Aug 22, 2007, at 3:37 PM, Joshua D. Drake wrote:
You can not do multi master cross continent reliably.
I'm pretty sure that credit card processors and some other companies
do it... it just costs a LOT to actually do it well.
--
Decibel!, aka Jim Nasby[EMAIL PROTECT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthew wrote:
> Hey all, new postgres user here. We are trying to setup/research an
> HA/Replicated solution with Postrgresql between a datacenter in LA and a
> d.c. in NY.
>
> We have a private LAN link between the two D.C.'s with a max round-trip
>
Hey all, new postgres user here. We are trying to setup/research an
HA/Replicated solution with Postrgresql between a datacenter in LA and a
d.c. in NY.
We have a private LAN link between the two D.C.'s with a max round-trip
of 150ms.
We will have a web server at each d.c. (among other servers) t
18 matches
Mail list logo
