John R Pierce pie...@hogranch.com writes:
yeah. generally when money is involved in the transactions, you gotta stick
to the 'no committed data lost ever'. there's plenty of other use cases for
that too.
Well, it's a cost/benefit/risk evaluation you have to make. It'd be bad
news that the
On 23/06/10 03:05, John R Pierce wrote:
yeah. generally when money is involved in the transactions, you gotta
stick to the 'no committed data lost ever'. there's plenty of other use
cases for that too.
2PC is sometimes a reasonable alternative to shared-storage failover,
though. It can be a
On Mon, 2010-06-21 at 23:08 -0400, Greg Smith wrote:
The hard part of shared storage failover is always solving the shoot
the other node in the head problem, to keep a down node from coming
back once it's no longer the active one. In order to do that well,
you really need to lock the now
John R Pierce pie...@hogranch.com writes:
failure modes can
include things like failing fans (which will be detected, resulting in a
server shutdown if too many fail), power supply failure (redundant PSUs, but
I've seen the power combining circuitry fail). Any of these sorts of
failures
John R Pierce wrote:
I don't like power cycling servers, so I'd prefer not to use power
switch based fencing, although I believe my blade box's management
unit is supported as a power fencing device.
I consider power control fencing to be a secondary resort if you don't
have hardware where a
On 06/22/10 1:58 AM, Dimitri Fontaine wrote:
John R Piercepie...@hogranch.com writes:
failure modes can
include things like failing fans (which will be detected, resulting in a
server shutdown if too many fail), power supply failure (redundant PSUs, but
I've seen the power combining
John R Pierce pie...@hogranch.com writes:
Two DB servers will be using a common external storage (with raid).
This is also one of the only postgres HA configurations that won't lose
/any/ committed transactions on a failure. Most all PITR/WAL
replication/Slony/etc configs, the standby
On 06/21/10 12:23 PM, Dimitri Fontaine wrote:
John R Piercepie...@hogranch.com writes:
Two DB servers will be using a common external storage (with raid).
This is also one of the only postgres HA configurations that won't lose
/any/ committed transactions on a failure. Most all
John R Pierce wrote:
the commercial cluster software vendors insist on using dedicated
connections for the heartbeat messages between the cluster members and
insist on having fencing capabilities (for instance, disabling the
fiber switch port of the formerly active server and enabling the port
On 06/21/10 8:08 PM, Greg Smith wrote:
The hard part of shared storage failover is always solving the shoot
the other node in the head problem, to keep a down node from coming
back once it's no longer the active one. In order to do that well,
you really need to lock the now unavailable node
Hello,
My company looking for some solution for High availability with Postgres.
Our optional solution is as follows :
Two DB servers will be using a common external storage (with raid). Both
servers are going to use the same DB files on the storage (as
active/passive)
Now I'm trying to
On Sun, Jun 20, 2010 at 07:34:10PM +0300, Elior Soliman wrote:
Hello,
My company looking for some solution for High availability with Postgres.
Our optional solution is as follows :
Two DB servers will be using a common external storage (with raid).
Stop right there. This is the Oracle
On 21/06/10 00:34, Elior Soliman wrote:
Hello,
My company looking for some solution for High availability with Postgres.
Our optional solution is as follows :
Two DB servers will be using a common external storage (with raid). Both
servers are going to use the same DB files on the storage
On 06/20/10 10:36 AM, David Fetter wrote:
On Sun, Jun 20, 2010 at 07:34:10PM +0300, Elior Soliman wrote:
My company looking for some solution for High availability with Postgres.
Our optional solution is as follows :
Two DB servers will be using a common external storage (with raid).
On 20/06/2010 17:34, Elior Soliman wrote:
Hello,
My company looking for some solution for High availability with Postgres.
There's quite a bit of information in the documentation here:
http://www.postgresql.org/docs/8.4/static/high-availability.html
HTH,
Ray.
--
Raymond O'Donnell ::
Hi,
On 21/06/2010, at 3:37 AM, Raymond O'Donnell wrote:
On 20/06/2010 17:34, Elior Soliman wrote:
Hello,
My company looking for some solution for High availability with
Postgres.
There's quite a bit of information in the documentation here:
16 matches
Mail list logo
