From: Markus Schiltknecht <markus@bluegap.ch>
To: anorganic anorganic <anorganicphc@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Replication
Date: Thu, 04 Jan 2007 13:00:16 +0100
Message-ID: <459CEC50.6030407@bluegap.ch> (raw)
In-Reply-To: <f616803e0701040237p4f4fe26atc2eba1b2a9b8a1d3@mail.gmail.com>
References: <f616803e0701040100p5958ee2dy56924ee326c23e0d@mail.gmail.com>
<459CC52A.4030208@bluegap.ch>
<f616803e0701040140u18e27769r54ac39d79be29519@mail.gmail.com>
<459CD1D1.8010002@bluegap.ch>
<f616803e0701040237p4f4fe26atc2eba1b2a9b8a1d3@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: markus@bluegap.ch, anorganicphc@gmail.com
Subject: Re: Replication
In-Reply-To: <459CEC50.6030407@bluegap.ch>
References: <f616803e0701040100p5958ee2dy56924ee326c23e0d@mail.gmail.com> <459CC52A.4030208@bluegap.ch> <f616803e0701040140u18e27769r54ac39d79be29519@mail.gmail.com> <459CD1D1.8010002@bluegap.ch> <f616803e0701040237p4f4fe26atc2eba1b2a9b8a1d3@mail.gmail.com> <459CEC50.6030407@bluegap.ch>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox