Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 043CF9F931E for ; Thu, 4 Jan 2007 08:00:30 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 98917-07 for ; Thu, 4 Jan 2007 08:00:15 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from bugaboo.mu (ns1.bugaboo.mu [213.133.111.57]) by postgresql.org (Postfix) with ESMTP id 06C8B9FA2FC for ; Thu, 4 Jan 2007 08:00:18 -0400 (AST) Received: from [192.168.0.237] (berlin.programmfabrik.de [::ffff:213.221.101.147]) (AUTH: CRAM-MD5 markus@bluegap.ch) by bugaboo.mu with esmtp; Thu, 04 Jan 2007 13:00:17 +0100 id 020253D7.459CEC51.000039AF Message-ID: <459CEC50.6030407@bluegap.ch> Date: Thu, 04 Jan 2007 13:00:16 +0100 From: Markus Schiltknecht User-Agent: Icedove 1.5.0.9 (X11/20061220) MIME-Version: 1.0 To: anorganic anorganic CC: pgsql-admin@postgresql.org Subject: Re: Replication References: <459CC52A.4030208@bluegap.ch> <459CD1D1.8010002@bluegap.ch> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/23 X-Sequence-Number: 24179 Hi, [ please keep CCing to the list (reply all), as this certainly isn't a personal discussion and could help others. ] anorganic anorganic wrote: > Hello, > > "I don't quite follow what you mean here. I assume you mean rows, not > columns. Then probably you mean something like what we call data > partitioning, where each server is a master for a certain subset of the > data." > > I think granurality, some system allow replicate only all db, all table, > some allow to choose only 4 colums from one table 2 from another and > replicated only these parts of db. I can add example. > it's not partitioning. Uhm.. I'd still call it partitioning. Although, I'm not exactly sure why you want to replicate only a partial row. I suspect you will have to split into two tables and have one table replicated while not replicating the other. > "Interesting... where exactly is it to short for you? What else would you > expect?" > > ok may be i'm false but i think this all is not common features of postgre > and it's necessary use system as slony. > i want know what i must use, how i can make and detail description of these > solution. What's happen when connection crash, when server shutdown etc. Right, but as we only have external solutions, I think it makes sense to have them document how exactly they work and behave. > "Hm. If that really is a problem, think again about sync vs. async. In > async replication, there is a delay by definition. But again, I'm not > sure what Slony can do to minimize that delay." > > yeah may be i am on bad adress but may be somebody here will say me here i > used this program fort his solution. Or this problem have no solution on > postgre. I fear replication is such a wide field with that many options, you probably can't get away with a general approach. I especially think so because I consider your wishes to be quite exotic for two reasons: * realtime, as fast as possible, but certainly not sync (You are aware that async, no matter how fast, can lead to conflicts, aren't you?) * replicating only parts of a row > Async, sync i dont need sync, but i need send change fast as possible. i > don't want sync. But when i change col on s1 i wnat send change right now, > no waiting for another 5 changes. It must be quite realtime we have low > traffic between servers there is not necessary make some optimilaztion as > sending in packages. I'd be surprised if Slony couldn't be configured to send changes immediately (i.e. not waiting for more transactions before sending a package). But again, the Slony guys may know better. Regards Markus