Re: [GENERAL] - PostgreSQL Replication Types

On 12/17/2015 07:56 AM, Will McCormick wrote: Thanks a ton for the prompt response. I've read most of this but some it was not clear until we discussed. See here for more detail: WLM: Reading now :) While reading I would suggest having the postgres.conf files on the master and the

Re: [GENERAL] - PostgreSQL Replication Types

Thanks for the great assistance On Thu, Dec 17, 2015 at 11:27 AM, Adrian Klaver wrote: > On 12/17/2015 07:56 AM, Will McCormick wrote: > >> Thanks a ton for the prompt response. >> >> I've read most of this but some it was not clear until we discussed. >> >> Updated

Re: [GENERAL] - PostgreSQL Replication Types

Hi Will, On 12/17/15 10:17 AM, Will McCormick wrote: > I inherited a 9.1 replication environment > > Few basic questions that I can't find clear answers / clarifications for > if possible: > > 3 types of replication in 9.1 I've read about from the offical docs: > > 1) warm standby This is a

[GENERAL] - PostgreSQL Replication Types

I inherited a 9.1 replication environment Few basic questions that I can't find clear answers / clarifications for if possible: 3 types of replication in 9.1 I've read about from the offical docs: 1) warm standby 2) hot standby 3) streaming replication I'm using streaming replication I

Re: [GENERAL] - PostgreSQL Replication Types

On 12/17/2015 07:56 AM, Will McCormick wrote: Thanks a ton for the prompt response. I've read most of this but some it was not clear until we discussed. Updated with WLM: On 12/17/2015 07:17 AM, Will McCormick wrote: I inherited a 9.1 replication environment Few basic questions that

Re: [GENERAL] - PostgreSQL Replication Types

Almost forgot this: SELECT pg_current_xlog_location(); ERROR: recovery is in progress HINT: WAL control functions cannot be executed during recovery. bms=> SELECT pg_current_xlog_location(); ERROR: recovery is in progress HINT: WAL control functions cannot be executed during recovery.

Re: [GENERAL] - PostgreSQL Replication Types

On 12/17/2015 07:17 AM, Will McCormick wrote: I inherited a 9.1 replication environment Few basic questions that I can't find clear answers / clarifications for if possible: 3 types of replication in 9.1 I've read about from the offical docs: 1) warm standby 2) hot standby 3) streaming

Re: [GENERAL] - PostgreSQL Replication Types

Thanks a ton for the prompt response. I've read most of this but some it was not clear until we discussed. Updated with WLM: On 12/17/2015 07:17 AM, Will McCormick wrote: > > I inherited a 9.1 replication environment > > Few basic questions that I can't find clear answers / clarifications for >

Re: [GENERAL] - PostgreSQL Replication Types

On 12/17/2015 08:43 AM, Will McCormick wrote: Almost forgot this: SELECT pg_current_xlog_location(); I was not paying attention earlier that should be: pg_last_xlog_receive_location() from: http://www.postgresql.org/docs/9.1/interactive/functions-admin.html Table 9-58. Recovery

Re: [GENERAL] Postgresql replication assistance

Gustav Potgieter wrote: Hope you can assist and that I am posting to the right forum. Sending the question twice with the same wording does not make it clearer... We currently have multiple Postgresql 9 instances running with warm standby, and the replication work wonderfully. The problem

[GENERAL] Postgresql replication assistance

Hi All, Hope you can assist and that I am posting to the right forum. We currently have multiple Postgresql 9 instances running with warm standby, and the replication work wonderfully. The problem is the following, we take the slave database out of recovery and it works perfectly, but when we

[GENERAL] Postgresql replication assistance

Hi All, Hope you can assist and that I am posting to the right forum. We currently have multiple Postgresql 9 instances running with warm standby, and the replication work wonderfully. The problem is the following, we take the slave database out of recovery and it works perfectly, but when we

[GENERAL] Postgresql Replication Comparison Required

I am doing POC on Posgtresql replication. I am using latest version of postgresql i.e. 9.1. There are multiple replication solutions avaliable in the market (PGCluster, Pgpool-II, Slony-I). Postgresql also provide in-built replication solutions (Streaming replication, Warm Standby and hot

Re: [GENERAL] Postgresql Replication Comparison Required

Hello, in general my advice would be to stick with native features, therefore use either Streaming Replication (or alternatively log shipping replication). You might need some tools to help you manage the cluster, clients routing and balancing but I suggest you look into this later. On Thu,

Re: [GENERAL] PostgreSQL Replication with read-only access to standby DB

On Mar 25, 2008, at 4:28 PM, Jeff Davis wrote: This obviously does not work in real time, but it may be useful. It does not require a lot of additional space to do this because of the ZFS copy-on-write implementation. But what benefit does it give you if you're pounding on the same set of

Re: [GENERAL] PostgreSQL Replication with read-only access to standby DB

On Tue, 2008-03-25 at 17:53 -0600, Keaton Adams wrote: That is an interesting question. If our organization were to help fund the development of such a feature, would that be something taken into consideration by the development team? Yes. Many of my major projects have been funded that way.

[GENERAL] PostgreSQL Replication with read-only

Our organization is looking for a hot-standby option for PostgreSQL that uses the WAL (transaction) data to keep the standby current and also allows the standby to be read-only accessible for reporting. We have implemented WAL shipping through a set of scripts we developed and that works well to

Re: [GENERAL] PostgreSQL Replication with read-only access to standby DB

Le mercredi 26 mars 2008, Greg Smith a écrit : (My favorite acronym is TLA) Hehe :) I'd vote for A... -- dim signature.asc Description: This is a digitally signed message part.

Re: [GENERAL] PostgreSQL Replication with read-only access to standby DB

On Wed, Mar 26, 2008 at 01:03:34AM -0400, Greg Smith wrote: against. People who are using the current warm-standby code are already grappling with issues like how to coordinate master/slave failover (including my second favorite acronym, STONITH for shoot the other node in the head). I

Re: [GENERAL] PostgreSQL Replication with read-only access to standby DB

[EMAIL PROTECTED] (Keaton Adams) writes: That is an interesting question. If our organization were to help fund the development of such a feature, would that be something taken into consideration by the development team? I seem to recall there being a relevant Google Summer of Code project

Re: [GENERAL] PostgreSQL Replication with read-only access to standby DB

Chris Browne wrote: I seem to recall there being a relevant Google Summer of Code project about this, last year. I do not recall how far it got. It obviously didn't make it into 8.3 ;-)! Some parts of it did -- for example we got read-only transactions which were a step towards that goal.

[GENERAL] PostgreSQL Replication with read-only access to standby DB

Our organization is looking for a hot-standby option for PostgreSQL that uses the WAL (transaction) data to keep the standby current and also allows the standby to be read-only accessible for reporting. We have implemented WAL shipping through a set of scripts we developed and that works well to

Re: [GENERAL] PostgreSQL Replication with read-only access to standby DB

Keaton Adams wrote: Our organization is looking for a hot-standby option for PostgreSQL that uses the WAL (transaction) data to keep the standby current and also allows the standby to be read-only accessible for reporting. We have implemented WAL shipping through a set of scripts we developed

Re: [GENERAL] PostgreSQL Replication with read-only access to standby DB

On Tue, Mar 25, 2008 at 1:17 PM, salman [EMAIL PROTECTED] wrote: IIRC, it was mentioned previously in one posting that this a TODO for a future version of postgres but not something that's expected soon. Someone please correct me if I'm wrong. This is what I saw on the TODO list: Write-Ahead

Re: [GENERAL] PostgreSQL Replication with read-only access to standby DB

But will that stand-by replication provide for a read-only slave? On 3/25/08 2:26 PM, Richard Broersma [EMAIL PROTECTED] wrote: On Tue, Mar 25, 2008 at 1:17 PM, salman [EMAIL PROTECTED] wrote: IIRC, it was mentioned previously in one posting that this a TODO for a future version of postgres

Re: [GENERAL] PostgreSQL Replication with read-only access to standby DB

On Tue, 2008-03-25 at 14:11 -0600, Keaton Adams wrote: “All queries reading from the physical replica execute in real-time, and return current results. A Data Guard configuration consists of one production (or primary) database and up to nine standby databases. A standby database is

Re: [GENERAL] PostgreSQL Replication with read-only access to standby DB

It is close, but has limitations that will be problematic for our environment, such as: Replicator will not replicate the schema. You must restore your schema to th e slaves from the master before you begin replication. Replicator can only replicate one database. If you have multiple databases 

Re: [GENERAL] PostgreSQL Replication with read-only access to standby DB

On Tue, 2008-03-25 at 14:11 -0600, Keaton Adams wrote: “Oracle Active Data Guard enables a physical standby database to be open for read-only access – for reporting, simple or complex queries – while changes from the production database are being applied to it. This means any operation that

Re: [GENERAL] PostgreSQL Replication with read-only access to standby DB

On Tue, Mar 25, 2008 at 3:08 PM, Simon Riggs [EMAIL PROTECTED] wrote: On Tue, 2008-03-25 at 14:11 -0600, Keaton Adams wrote: Some funding would help that move forwards. If you or others would consider that, it would help, even if just to provide the seed for additional contributors. That is

Re: [GENERAL] PostgreSQL Replication with read-only access to standby DB

On Tue, Mar 25, 2008 at 1:11 PM, Keaton Adams [EMAIL PROTECTED] wrote: Our organization is looking for a hot-standby option for PostgreSQL that uses the WAL (transaction) data to keep the standby current and also allows the standby to be read-only accessible for reporting. We have implemented

Re: [GENERAL] PostgreSQL Replication with read-only access to standby DB

That is an interesting question. If our organization were to help fund the development of such a feature, would that be something taken into consideration by the development team? -Keaton On 3/25/08 4:32 PM, Richard Broersma [EMAIL PROTECTED] wrote: On Tue, Mar 25, 2008 at 3:08 PM, Simon

Re: [GENERAL] PostgreSQL Replication with read-only access to standby DB

Similar case has been already happened. For example, I have propsed to implement WITH RECURSIVE clause and the work is supported by Sumitomo Electric Information Systems Co., Ltd. (http://www.sei-info.co.jp/) and SRA OSS, Inc. Japan (http://www.sraoss.co.jp). -- Tatsuo Ishii SRA OSS, Inc. Japan

Re: [GENERAL] PostgreSQL Replication with read-only access to standby DB

, 2008 4:29 PM To: Richard Broersma; salman Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] PostgreSQL Replication with read-only access to standby DB But will that stand-by replication provide for a read-only slave? On 3/25/08 2:26 PM, Richard Broersma [EMAIL PROTECTED] wrote: On Tue

Re: [GENERAL] PostgreSQL Replication with read-only access to standby DB

On Tue, 25 Mar 2008, Jonathan Bond-Caron wrote: I know very little about postgreSQL internals but it would be great if: - WAL files could be applied while the standby server is operational / allow read-only queries This is the part that requires modifying PostgreSQL, and that progress was

Re: [GENERAL] PostGreSQL Replication

Sounds like something you'd want to handle within the application I believe i will try to follow this path. ---(end of broadcast)--- TIP 6: explain analyze is your friend

Re: [GENERAL] PostGreSQL Replication

On Sat, Jul 07, 2007 at 05:16:56AM -0700, Gabriele wrote: Let's have a server which feed data to multiple slaves, usually using direct online connections. Now, we may want to allow those client to sync the data to a local replica, work offline and then resync the data back to the server. Which

Re: [GENERAL] PostGreSQL Replication

On 07.07.2007, at 06:16, Gabriele wrote: Let's have a server which feed data to multiple slaves, usually using direct online connections. Now, we may want to allow those client to sync the data to a local replica, work offline and then resync the data back to the server. Which is the easiest

Re: [GENERAL] PostGreSQL Replication

On Saturday 07 July 2007 14.16:56 Gabriele wrote: I know this is a delicate topic which must be approached cautiously. Let's have a server which feed data to multiple slaves, usually using direct online connections. Now, we may want to allow those client to sync the data to a local replica,

[GENERAL] PostGreSQL Replication

I know this is a delicate topic which must be approached cautiously. Let's have a server which feed data to multiple slaves, usually using direct online connections. Now, we may want to allow those client to sync the data to a local replica, work offline and then resync the data back to the

Re: [GENERAL] PostgreSql replication and load balancing ( is Slony-I a solution?)

On 5/2/07, Jamie Deppeler [EMAIL PROTECTED] wrote: You might want to check pgcluster out http://pgcluster.projects.postgresql.org/ witch does both. That page will give you the impression that this project is dead and abandoned -- the last update is from early 2005. PGCluster does seem to be

Re: [GENERAL] PostgreSql replication and load balancing ( is Slony-I a solution?)

Alexander Staubo wrote: On 5/2/07, Jamie Deppeler [EMAIL PROTECTED] wrote: You might want to check pgcluster out http://pgcluster.projects.postgresql.org/ witch does both. That page will give you the impression that this project is dead and abandoned -- the last update is from early 2005.

Re: [GENERAL] PostgreSql replication and load balancing ( is Slony-I a solution?)

On 5/2/07, Alvaro Herrera [EMAIL PROTECTED] wrote: Alexander Staubo wrote: On 5/2/07, Jamie Deppeler [EMAIL PROTECTED] wrote: You might want to check pgcluster out http://pgcluster.projects.postgresql.org/ witch does both. That page will give you the impression that this project is dead and

Re: [GENERAL] PostgreSql replication and load balancing ( is Slony-I a solution?)

Alexander Staubo wrote: On 5/2/07, Alvaro Herrera [EMAIL PROTECTED] wrote: Alexander Staubo wrote: On 5/2/07, Jamie Deppeler [EMAIL PROTECTED] wrote: You might want to check pgcluster out http://pgcluster.projects.postgresql.org/ witch does both. That page will give you the impression

Re: [GENERAL] PostgreSql replication and load balancing ( is Slony-I a solution?)

On 5/2/07, Alvaro Herrera [EMAIL PROTECTED] wrote: They're different pages. The first one is horribly out of date; unfortunately, it is (for me) the first hit on Google, whereas the PgFoundry project page is the third. Sure, they are different pages, but the first one is supposed to be

Re: [GENERAL] PostgreSql replication and load balancing ( is Slony-I a solution?)

Alexander Staubo wrote: On 5/2/07, Alvaro Herrera [EMAIL PROTECTED] wrote: They're different pages. The first one is horribly out of date; unfortunately, it is (for me) the first hit on Google, whereas the PgFoundry project page is the third. Sure, they are different pages, but the first

[GENERAL] PostgreSql replication and load balancing ( is Slony-I a solution?)

Hello, We're building database system with replication. Slony-I seems to be a quite good solution for the replication, but beside the replication (master-to-multiple slaves), we need load balancing aswell - multiple users will access the database at the same time=multiple queries. Is Slony-I

Re: [GENERAL] PostgreSql replication and load balancing ( is Slony-I a solution?)

On 5/1/07, Jan Bilek [EMAIL PROTECTED] wrote: Is Slony-I capable of load balancing and how to set it up? We searched the web and some people mentioned that Slony-I could do load balancing, but haven't found how to make Slony-I to do it. Slony does not do load balancing. Personally, I recommend

Re: [GENERAL] PostgreSql replication and load balancing ( is Slony-I a solution?)

On 5/1/07, Jan Bilek [EMAIL PROTECTED] wrote: Is Slony-I capable of load balancing and how to set it up? We searched the web and some people mentioned that Slony-I could do load balancing, but haven't found how to make Slony-I to do it. Slony does not do load balancing. Personally, I

Re: [GENERAL] PostgreSql replication and load balancing ( is Slony-I a solution?)

Alexander Staubo wrote: On 5/1/07, Jan Bilek [EMAIL PROTECTED] wrote: Is Slony-I capable of load balancing and how to set it up? We searched the web and some people mentioned that Slony-I could do load balancing, but haven't found how to make Slony-I to do it. You might want to check

Re: [GENERAL] Postgresql Replication

Nareen S wrote: Current Setup I am having a Mailserver running on Postfix.For the same I had configured a High Availability Solution using Heartbeat and DRBD for replication.Thesetup is like Primary/Secondary Node Servers and all mails are replicated to secondary using DRBD.If primary server

Re: [GENERAL] Postgresql Replication

Richard Huxton dev@archonet.com wrote: Nareen S wrote: Current Setup I am having a Mailserver running on Postfix.For the same I had configured a High Availability Solution using Heartbeat and DRBD for replication.Thesetup is like Primary/Secondary Node Servers and all mails are replicated

[GENERAL] Postgresql Replication

Current Setup I am having a Mailserver running on Postfix.For the same I had configured a High Availability Solution using Heartbeat and DRBD for replication.The setup is like Primary/Secondary Node Servers and all mails are replicated to secondary using DRBD.If primary server fails secondary

Re: [GENERAL] Postgresql replication

On Thu, Aug 25, 2005 at 01:44:15PM +0200, Bohdan Linda wrote: there are some other db solutions which have good performance when doing this kind of replication across the world. Bluntly, No. -- Andrew Sullivan | [EMAIL PROTECTED] Information security isn't a technological problem. It's an

Re: [GENERAL] Postgresql replication

On Wed, Aug 24, 2005 at 11:54:42AM -0400, Chris Browne wrote: There is a Slony-II project ongoing that is trying to construct a more-or-less synchronous multimaster replication system (where part of the cleverness involves trying to get as much taking place in an asynchronous fashion as

Re: [GENERAL] Postgresql replication

Chris Travers wrote: 1) Efficiency of network throughput 2) Tolerance to attempts at repeat transactions before replication (emptying an account multiple times) 3) Availability of a transaction. We ended up having to give up #1. It's possible to have our transactions routed to multiple

Re: [GENERAL] Postgresql replication

William Yu wrote: Chris Travers wrote: 1) Efficiency of network throughput 2) Tolerance to attempts at repeat transactions before replication (emptying an account multiple times) 3) Availability of a transaction. We ended up having to give up #1. It's possible to have our

Re: [GENERAL] Postgresql replication

Our own personal IM :) Chris Travers wrote: The delay will by definition defeat any guarantee of financial integrity if you are allowing read-write operations to the replica without checking with some sort of central authority. At very least, the central authority should look for suspicious

Re: [GENERAL] Postgresql replication

William Yu [EMAIL PROTECTED] writes: Chris Browne wrote: I'm pretty sure that they _don't_ track balance updates for each transaction that applies to a customer's account. You could, via one form of trickery or another, overdraw your account by a fairly hefty amount, and they probably won't

Re: [GENERAL] Postgresql replication

Chris Travers wrote: Why not have the people who have rights to review this all write to the master database and have that replicated back? It seems like latency is not really an issue. Replication here is only going to complicate What master database? Having a single master defeats the

Re: [GENERAL] Postgresql replication

William Yu wrote: This system sounds ok for documents and general data that can always be revived via version control/history. But I can't see how this would work for financial transactions where you're dealing with money and bank accounts. Suppose I have $100 in my account. I decided to

Re: [GENERAL] Postgresql replication

Hi, I´mthinking to test your suggestion, basically because there are only few sites to connect, but there are some points that aren´t very clear to me. My doubts: 1. How to make a view updatable? Using the rule system? 1. Why are insertshandled differently from updates? 2. Can not I use the

Re: [GENERAL] Postgresql replication

[EMAIL PROTECTED] (Chris Travers) writes: William Yu wrote: This system sounds ok for documents and general data that can always be revived via version control/history. But I can't see how this would work for financial transactions where you're dealing with money and bank accounts. Suppose I

Re: [GENERAL] Postgresql replication

William Yu wrote: Chris Travers wrote: Why not have the people who have rights to review this all write to the master database and have that replicated back? It seems like latency is not really an issue. Replication here is only going to complicate What master database? Having a

Re: [GENERAL] Postgresql replication

On Thu, 2005-08-25 at 17:45 -0700, Jeff Davis wrote: The replicator surely is not optional, and must be centralized. From http://pgcluster.projects.postgresql.org/1_3/index.html: Several replication server can be set up. When an problem occurs at the replication server, Cluster DB automatically

Re: [GENERAL] Postgresql replication

Chris Travers wrote: I guess I am thinking along different lines than you. I was thinking that the simplest solution would be to have master/slave replication for *approved* transactions only and no replication for initial commits prior to approval. This makes the assumption that a single

Re: [GENERAL] Postgresql replication

William Yu wrote: Chris Travers wrote: I guess I am thinking along different lines than you. I was thinking that the simplest solution would be to have master/slave replication for *approved* transactions only and no replication for initial commits prior to approval. This makes the

Re: [GENERAL] Postgresql replication

Carlos Henrique Reimer wrote: I read some documents about replication and realized that if you plan on using asynchronous replication, your application should be designed from the outset with that in mind because asynchronous replication is not something that can be easily “added on” after

Re: [GENERAL] Postgresql replication

It provides pseudo relief if all your servers are in the same building. Having a front-end pgpool connector pointing to servers across the world is not workable -- performance ends up being completely decrepit due to the high latency. Which is the problem we face. Great, you've got multiple

Re: [GENERAL] Postgresql replication

I would have a slight offtopic question, this is issue only of pgsql or there are some other db solutions which have good performance when doing this kind of replication across the world. Regards, Bohdan On Thu, Aug 25, 2005 at 09:01:49AM +0200, William Yu wrote: It provides pseudo relief if

Re: [GENERAL] Postgresql replication

Bohdan Linda schrieb: I would have a slight offtopic question, this is issue only of pgsql or there are some other db solutions which have good performance when doing this kind of replication across the world. it depends entirely on your application. There is no one size fits all For example

Re: [GENERAL] Postgresql replication

As far as I know, nobody has a generic solution for multi-master replication where servers are not in close proximity. Single master replication? Doable. Application specific conflict resolution? Doable. Off the shelf package that somehow knows financial transactions on a server shouldn't be

Re: [GENERAL] Postgresql replication

Another tidbit I'd like to add. What has helped a lot in implementing high-latency master-master replication writing our software with a business process model in mind where data is not posted directly to the final tables. Instead, users are generally allowed to enter anything -- could be

Re: [GENERAL] Postgresql replication

Tino Wildenhain wrote: Which is the problem we face. Great, you've got multiple servers for failover. Too bad it doesn't do much good if your building gets hit by fire/earthquake/hurricane/etc. This would remove the application using that data too, or not? ;) Yes and no. If your DB is an

Re: [GENERAL] Postgresql replication

On Thursday 25 August 2005 13:03, William Yu wrote: As far as I know, nobody has a generic solution for multi-master replication where servers are not in close proximity. Single master replication? Doable. Application specific conflict resolution? Doable. Off the shelf package that somehow

Re: [GENERAL] Postgresql replication

Chris Travers wrote: Carlos Henrique Reimer wrote: I read some documents about replication and realized that if you plan on using asynchronous replication, your application should be designed from the outset with that in mind because asynchronous replication is not something that can be

Re: [GENERAL] Postgresql replication

Bohdan Linda wrote: I would have a slight offtopic question, this is issue only of pgsql or there are some other db solutions which have good performance when doing this kind of replication across the world. It all depends on the quality of the connection Node A to Node B. If connectivity

Re: [GENERAL] Postgresql replication

William Yu schrieb: Tino Wildenhain wrote: Which is the problem we face. Great, you've got multiple servers for failover. Too bad it doesn't do much good if your building gets hit by fire/earthquake/hurricane/etc. This would remove the application using that data too, or not? ;) Yes

Re: [GENERAL] Postgresql replication

[EMAIL PROTECTED] (Aly Dharshi) writes: I know I am wadding into this discussion as an beginner compared to the rest who have answered this thread, but doesn't something like pgpool provide relief for pseudo-multimaster replication, and what about software like sqlrelay wouldn't these suites

Re: [GENERAL] Postgresql replication

[EMAIL PROTECTED] (David Goodenough) writes: On Thursday 25 August 2005 13:03, William Yu wrote: As far as I know, nobody has a generic solution for multi-master replication where servers are not in close proximity. Single master replication? Doable. Application specific conflict resolution?

Re: [GENERAL] Postgresql replication

[EMAIL PROTECTED] (Bohdan Linda) writes: I would have a slight offtopic question, this is issue only of pgsql or there are some other db solutions which have good performance when doing this kind of replication across the world. Asynchronous multimaster replication is pretty much a generally

Re: [GENERAL] Postgresql replication

Jim C. Nasby wrote: Or, for something far easier, try http://pgfoundry.org/projects/pgcluster/ which provides syncronous multi-master clustering. He specifically said that pgcluster did not work for him because the databases would be at physically seperate locations. PGCluster requires that

Re: [GENERAL] Postgresql replication

ExactlyJeff Davis [EMAIL PROTECTED] escreveu: Jim C. Nasby wrote: Or, for something far easier, try http://pgfoundry.org/projects/pgcluster/ which provides syncronous multi-master clustering. He specifically said that pgcluster did not work for him because thedatabases would be at physically

Re: [GENERAL] Postgresql replication

http://pgfoundry.org/projects/pgcluster/ which provides syncronous multi-master clustering. He specifically said that pgcluster did not work for him because ...PGCluster requires that there be a load balancer and a replicator centrally located managing the cluster. If a network problem

Re: [GENERAL] Postgresql replication

On Thu, Aug 25, 2005 at 12:20:52PM -0400, Chris Browne wrote: [EMAIL PROTECTED] (Bohdan Linda) writes: I would have a slight offtopic question, this is issue only of pgsql or there are some other db solutions which have good performance when doing this kind of replication across the world.

Re: [GENERAL] Postgresql replication

David Goodenough wrote: The most obvious one that does exactly this (generic multi-master replication) is Lotus Domino. It is not a relational DB, but not sufficiently far off to stop the analogy. Domino marks each document with a binary value which identifies the server (built from a hash of

Re: [GENERAL] Postgresql replication

Carlos Henrique Reimer wrote: Exactly Was there something lacking in my suggested solution at: http://archives.postgresql.org/pgsql-general/2005-08/msg01240.php It's a little complicated to administer, but it seems well-suited to a company that has several locations that want to share

Re: [GENERAL] Postgresql replication

[EMAIL PROTECTED] (Brad Nicholson) writes: Bohdan Linda wrote: I would have a slight offtopic question, this is issue only of pgsql or there are some other db solutions which have good performance when doing this kind of replication across the world. It all depends on the quality of the

Re: [GENERAL] Postgresql replication

[EMAIL PROTECTED] (Steve Atkins) writes: On Thu, Aug 25, 2005 at 12:20:52PM -0400, Chris Browne wrote: [EMAIL PROTECTED] (Bohdan Linda) writes: I would have a slight offtopic question, this is issue only of pgsql or there are some other db solutions which have good performance when doing

Re: [GENERAL] Postgresql replication

William Yu [EMAIL PROTECTED] writes: David Goodenough wrote: The most obvious one that does exactly this (generic multi-master replication) is Lotus Domino. It is not a relational DB, but not sufficiently far off to stop the analogy. Domino marks each document with a binary value which

Re: [GENERAL] Postgresql replication

William Yu wrote: Another tidbit I'd like to add. What has helped a lot in implementing high-latency master-master replication writing our software with a business process model in mind where data is not posted directly to the final tables. Instead, users are generally allowed to enter

Re: [GENERAL] Postgresql replication

Matt Miller wrote: http://pgfoundry.org/projects/pgcluster/ which provides syncronous multi-master clustering. He specifically said that pgcluster did not work for him because ...PGCluster requires that there be a load balancer and a replicator centrally located managing the cluster. If a network

[GENERAL] Postgresql replication

Hello, Currently we have only one database accessed by the headquarter and two branches but the performance in the branches is very poor and I was invited to discover a way to increase it. One possible solution is replicate the headquarter DB into the two branches. I read about slony-i, but

Re: [GENERAL] Postgresql replication

Am Mittwoch, 24. August 2005 14:21 schrieb Carlos Henrique Reimer: One possible solution is replicate the headquarter DB into the two branches. I read about slony-i, but then the replicated DBs will be read-only. That's because it's a master-slave replication. If you could sync the slave

Re: [GENERAL] Postgresql replication

[mailto:[EMAIL PROTECTED] Behalf Of Michael Meskes Am Mittwoch, 24. August 2005 14:21 schrieb Carlos Henrique Reimer: One possible solution is replicate the headquarter DB into the two branches. I read about slony-i, but then the replicated DBs will be read-only. That's because it's a

Re: [GENERAL] Postgresql replication

[EMAIL PROTECTED] (Carlos Henrique Reimer) writes: Currently we have only one database accessed by the headquarter and two branches but the performance in the  branches is very poor  and I was invited to discover a way to increase it. One possible solution is replicate the headquarter DB into

Re: [GENERAL] Postgresql replication

I read some documents about replicationand realized that if you plan on using asynchronous replication, your application should be designed from the outset with that in mind because asynchronous replication is not something that can be easily “added on” after the fact. Am I right? Reimer

Re: [GENERAL] Postgresql replication

Carlos Henrique Reimer wrote: I read some documents about replicationand realized that if you plan on using asynchronous replication, your application should be designed from the outset with that in mind because asynchronousreplication is not something that can be easily added on after

Re: [GENERAL] Postgresql replication

Chris Browne wrote: Slony-I is a master/slave asynchronous replication system; if you already considered it unsuitable, then I see little likelihood of other systems with the same sorts of properties being suitable. What could conceivably be of use to you would be a *multimaster*

Re: [GENERAL] Postgresql replication

Jeff Davis writes: I hope this is helpful. Let me know if there's some reason my plan won't work. look at the solution in pgreplicator. site ids are embedded in the id columns in the tables, so there only m tables, and a bit less insanity. That doesn't work with Slony-I unfortunately. I

Re: [GENERAL] Postgresql replication

Welty, Richard wrote: Jeff Davis writes: The disadvantages: one more: if you actually have m tables and n servers, you have m x n tables in reality, which is pretty miserable scaling behavior. i should think that rules, triggers, and embedded procedures would explode in complexity

  1   2   >