Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 4404c9a

Browse files
bmomjianbmomjian
committed
Add to replication.
1 parent c0e7846 commit 4404c9a

File tree

1 file changed

+169
-7
lines changed

1 file changed

+169
-7
lines changed

‎doc/TODO.detail/replication

Lines changed: 169 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ From [email protected] Fri Dec 24 10:01:18 1999
4343
Received: from renoir.op.net ([email protected] [207.29.195.4])
4444
by candle.pha.pa.us (8.9.0/8.9.0) with ESMTP id LAA11295
4545
for <[email protected]>; Fri, 24 Dec 1999 11:01:17 -0500 (EST)
46-
Received: from hub.org (hub.org [216.126.84.1]) by renoir.op.net (o1/$Revision: 1.8 $) with ESMTP id KAA20310 for <[email protected]>; Fri, 24 Dec 1999 10:39:18 -0500 (EST)
46+
Received: from hub.org (hub.org [216.126.84.1]) by renoir.op.net (o1/$Revision: 1.9 $) with ESMTP id KAA20310 for <[email protected]>; Fri, 24 Dec 1999 10:39:18 -0500 (EST)
4747
Received: from localhost (majordom@localhost)
4848
by hub.org (8.9.3/8.9.3) with SMTP id KAA61760;
4949
Fri, 24 Dec 1999 10:31:13 -0500 (EST)
@@ -129,7 +129,7 @@ From [email protected] Fri Dec 24 18:31:03 1999
129129
Received: from renoir.op.net ([email protected] [207.29.195.4])
130130
by candle.pha.pa.us (8.9.0/8.9.0) with ESMTP id TAA26244
131131
for <[email protected]>; Fri, 24 Dec 1999 19:31:02 -0500 (EST)
132-
Received: from hub.org (hub.org [216.126.84.1]) by renoir.op.net (o1/$Revision: 1.8 $) with ESMTP id TAA12730 for <[email protected]>; Fri, 24 Dec 1999 19:30:05 -0500 (EST)
132+
Received: from hub.org (hub.org [216.126.84.1]) by renoir.op.net (o1/$Revision: 1.9 $) with ESMTP id TAA12730 for <[email protected]>; Fri, 24 Dec 1999 19:30:05 -0500 (EST)
133133
Received: from localhost (majordom@localhost)
134134
by hub.org (8.9.3/8.9.3) with SMTP id TAA57851;
135135
Fri, 24 Dec 1999 19:23:31 -0500 (EST)
@@ -212,7 +212,7 @@ From [email protected] Fri Dec 24 21:31:10 1999
212212
Received: from renoir.op.net ([email protected] [207.29.195.4])
213213
by candle.pha.pa.us (8.9.0/8.9.0) with ESMTP id WAA02578
214214
for <[email protected]>; Fri, 24 Dec 1999 22:31:09 -0500 (EST)
215-
Received: from hub.org (hub.org [216.126.84.1]) by renoir.op.net (o1/$Revision: 1.8 $) with ESMTP id WAA16641 for <[email protected]>; Fri, 24 Dec 1999 22:18:56 -0500 (EST)
215+
Received: from hub.org (hub.org [216.126.84.1]) by renoir.op.net (o1/$Revision: 1.9 $) with ESMTP id WAA16641 for <[email protected]>; Fri, 24 Dec 1999 22:18:56 -0500 (EST)
216216
Received: from localhost (majordom@localhost)
217217
by hub.org (8.9.3/8.9.3) with SMTP id WAA89135;
218218
Fri, 24 Dec 1999 22:11:12 -0500 (EST)
@@ -486,7 +486,7 @@ From [email protected] Sun Dec 26 08:31:09 1999
486486
Received: from renoir.op.net ([email protected] [207.29.195.4])
487487
by candle.pha.pa.us (8.9.0/8.9.0) with ESMTP id JAA17976
488488
for <[email protected]>; Sun, 26 Dec 1999 09:31:07 -0500 (EST)
489-
Received: from hub.org (hub.org [216.126.84.1]) by renoir.op.net (o1/$Revision: 1.8 $) with ESMTP id JAA23337 for <[email protected]>; Sun, 26 Dec 1999 09:28:36 -0500 (EST)
489+
Received: from hub.org (hub.org [216.126.84.1]) by renoir.op.net (o1/$Revision: 1.9 $) with ESMTP id JAA23337 for <[email protected]>; Sun, 26 Dec 1999 09:28:36 -0500 (EST)
490490
Received: from localhost (majordom@localhost)
491491
by hub.org (8.9.3/8.9.3) with SMTP id JAA90738;
492492
Sun, 26 Dec 1999 09:21:58 -0500 (EST)
@@ -909,7 +909,7 @@ From [email protected] Thu Dec 30 08:01:09 1999
909909
Received: from renoir.op.net ([email protected] [207.29.195.4])
910910
by candle.pha.pa.us (8.9.0/8.9.0) with ESMTP id JAA10317
911911
for <[email protected]>; Thu, 30 Dec 1999 09:01:08 -0500 (EST)
912-
Received: from hub.org (hub.org [216.126.84.1]) by renoir.op.net (o1/$Revision: 1.8 $) with ESMTP id IAA02365 for <[email protected]>; Thu, 30 Dec 1999 08:37:10 -0500 (EST)
912+
Received: from hub.org (hub.org [216.126.84.1]) by renoir.op.net (o1/$Revision: 1.9 $) with ESMTP id IAA02365 for <[email protected]>; Thu, 30 Dec 1999 08:37:10 -0500 (EST)
913913
Received: from localhost (majordom@localhost)
914914
by hub.org (8.9.3/8.9.3) with SMTP id IAA87902;
915915
Thu, 30 Dec 1999 08:34:22 -0500 (EST)
@@ -1006,7 +1006,7 @@ From [email protected] Sun Jan 2 23:01:38 2000
10061006
Received: from renoir.op.net ([email protected] [207.29.195.4])
10071007
by candle.pha.pa.us (8.9.0/8.9.0) with ESMTP id AAA16274
10081008
for <[email protected]>; Mon, 3 Jan 2000 00:01:28 -0500 (EST)
1009-
Received: from hub.org (hub.org [216.126.84.1]) by renoir.op.net (o1/$Revision: 1.8 $) with ESMTP id XAA02655 for <[email protected]>; Sun, 2 Jan 2000 23:45:55 -0500 (EST)
1009+
Received: from hub.org (hub.org [216.126.84.1]) by renoir.op.net (o1/$Revision: 1.9 $) with ESMTP id XAA02655 for <[email protected]>; Sun, 2 Jan 2000 23:45:55 -0500 (EST)
10101010
Received: from hub.org (hub.org [216.126.84.1])
10111011
by hub.org (8.9.3/8.9.3) with ESMTP id XAA13828;
10121012
Sun, 2 Jan 2000 23:40:47 -0500 (EST)
@@ -1424,7 +1424,7 @@ From [email protected] Tue Jan 4 10:31:01 2000
14241424
Received: from renoir.op.net ([email protected] [207.29.195.4])
14251425
by candle.pha.pa.us (8.9.0/8.9.0) with ESMTP id LAA17522
14261426
for <[email protected]>; Tue, 4 Jan 2000 11:31:00 -0500 (EST)
1427-
Received: from hub.org (hub.org [216.126.84.1]) by renoir.op.net (o1/$Revision: 1.8 $) with ESMTP id LAA01541 for <[email protected]>; Tue, 4 Jan 2000 11:27:30 -0500 (EST)
1427+
Received: from hub.org (hub.org [216.126.84.1]) by renoir.op.net (o1/$Revision: 1.9 $) with ESMTP id LAA01541 for <[email protected]>; Tue, 4 Jan 2000 11:27:30 -0500 (EST)
14281428
Received: from localhost (majordom@localhost)
14291429
by hub.org (8.9.3/8.9.3) with SMTP id LAA09992;
14301430
Tue, 4 Jan 2000 11:18:07 -0500 (EST)
@@ -4887,3 +4887,165 @@ TIP 6: Have you searched our list archives?
48874887

48884888
http://www.postgresql.org/search.mpl
48894889

4890+
From [email protected] Wed Jun 13 09:05:56 2001
4891+
Return-path: <[email protected]>
4892+
Received: from postgresql.org (webmail.postgresql.org [216.126.85.28])
4893+
by candle.pha.pa.us (8.10.1/8.10.1) with ESMTP id f5DD5tE28260
4894+
for <[email protected]>; Wed, 13 Jun 2001 09:05:55 -0400 (EDT)
4895+
Received: from postgresql.org.org (webmail.postgresql.org [216.126.85.28])
4896+
by postgresql.org (8.11.3/8.11.1) with SMTP id f5DD5xE12437;
4897+
Wed, 13 Jun 2001 09:05:59 -0400 (EDT)
4898+
(envelope-from [email protected])
4899+
Received: from fizbanrsm.server.lan.at (zep4.it-austria.net [213.150.1.74])
4900+
by postgresql.org (8.11.3/8.11.1) with ESMTP id f5DD19E00635
4901+
for <[email protected]>; Wed, 13 Jun 2001 09:01:10 -0400 (EDT)
4902+
(envelope-from [email protected])
4903+
Received: from gz0153.gc.spardat.at (gz0153.gc.spardat.at [172.20.10.149])
4904+
by fizbanrsm.server.lan.at (8.11.2/8.11.2) with ESMTP id f5DD13m08153
4905+
for <[email protected]>; Wed, 13 Jun 2001 15:01:03 +0200
4906+
Received: by sdexcgtw01.f000.d0188.sd.spardat.at with Internet Mail Service (5.5.2650.21)
4907+
id <M6AB97MY>; Wed, 13 Jun 2001 15:00:02 +0200
4908+
Message-ID: <11C1E6749A55D411A9670001FA687963368322@sdexcsrv1.f000.d0188.sd.spardat.at>
4909+
From: Zeugswetter Andreas SB <[email protected]>
4910+
To: "'[email protected]'" <[email protected]>, [email protected]
4911+
Subject: AW: AW: AW: [HACKERS] Postgres Replication
4912+
Date: Wed, 13 Jun 2001 11:55:48 +0200
4913+
MIME-Version: 1.0
4914+
X-Mailer: Internet Mail Service (5.5.2650.21)
4915+
Content-Type: text/plain;
4916+
charset="iso-8859-1"
4917+
Precedence: bulk
4918+
Sender: [email protected]
4919+
Status: OR
4920+
4921+
4922+
> Well as I read back the thread I see 2 different approaches to
4923+
> replication:
4924+
>
4925+
> 1: tight integrated replication.
4926+
> pro:
4927+
> - bi-directional (or multidirectional): updates are possible everywhere
4928+
> - A cluster of servers allways has the same state.
4929+
> - it does not matter to which server you connect
4930+
> con:
4931+
> - network between servers will be a bottleneck, especially if it is a
4932+
> WAN connection
4933+
> - only full replication possible
4934+
4935+
I do not understand that point, if it is trigger based, you
4936+
have all the flexibility you need. (only some tables, only some rows,
4937+
different rows to different targets ....),
4938+
(or do you mean not all targets, that could also be achieved with triggers)
4939+
4940+
> - what happens if one server is down? (or the network between) are
4941+
> commits still possible
4942+
4943+
No, updates are not possible if one target is not reachable,
4944+
that would not be synchronous and would again need business rules
4945+
to resolve conflicts.
4946+
4947+
Allowing updates when a target is not reachable would require admin
4948+
intervention.
4949+
4950+
Andreas
4951+
4952+
---------------------------(end of broadcast)---------------------------
4953+
TIP 4: Don't 'kill -9' the postmaster
4954+
4955+
From [email protected] Wed Jun 13 11:15:48 2001
4956+
Return-path: <[email protected]>
4957+
Received: from postgresql.org (webmail.postgresql.org [216.126.85.28])
4958+
by candle.pha.pa.us (8.10.1/8.10.1) with ESMTP id f5DFFmE08382
4959+
for <[email protected]>; Wed, 13 Jun 2001 11:15:48 -0400 (EDT)
4960+
Received: from postgresql.org.org (webmail.postgresql.org [216.126.85.28])
4961+
by postgresql.org (8.11.3/8.11.1) with SMTP id f5DFFoE53621;
4962+
Wed, 13 Jun 2001 11:15:50 -0400 (EDT)
4963+
(envelope-from [email protected])
4964+
Received: from mail.greatbridge.com (mail.greatbridge.com [65.196.68.36])
4965+
by postgresql.org (8.11.3/8.11.1) with ESMTP id f5DEk7E38930
4966+
for <[email protected]>; Wed, 13 Jun 2001 10:46:07 -0400 (EDT)
4967+
(envelope-from [email protected])
4968+
Received: from j2.us.greatbridge.com (djohnsonpc.us.greatbridge.com [65.196.69.70])
4969+
by mail.greatbridge.com (8.11.2/8.11.2) with SMTP id f5DEhfQ22566;
4970+
Wed, 13 Jun 2001 10:43:41 -0400
4971+
From: Darren Johnson <[email protected]>
4972+
Date: Wed, 13 Jun 2001 14:44:11 GMT
4973+
Message-ID: <[email protected]>
4974+
Subject: Re: AW: AW: AW: [HACKERS] Postgres Replication
4975+
To: Zeugswetter Andreas SB <[email protected]>
4976+
cc: "'[email protected]'" <[email protected]>, [email protected]
4977+
Reply-To: Darren Johnson <[email protected]>
4978+
<11C1E6749A55D411A9670001FA687963368322@sdexcsrv1.f000.d0188.sd.spardat.at>
4979+
References: <11C1E6749A55D411A9670001FA687963368322@sdexcsrv1.f000.d0188.sd.spardat.at>
4980+
X-Mailer: Mozilla/3.0 (compatible; StarOffice/5.2;Linux)
4981+
X-Priority: 3 (Normal)
4982+
MIME-Version: 1.0
4983+
Content-Type: text/plain; charset=ISO-8859-1
4984+
Content-Transfer-Encoding: 8bit
4985+
X-MIME-Autoconverted: from quoted-printable to 8bit by postgresql.org id f5DEk8E38931
4986+
Precedence: bulk
4987+
Sender: [email protected]
4988+
Status: OR
4989+
4990+
4991+
> > - only full replication possible
4992+
4993+
> I do not understand that point, if it is trigger based, you
4994+
> have all the flexibility you need. (only some tables, only some rows,
4995+
> different rows to different targets ....),
4996+
> (or do you mean not all targets, that could also be achieved with
4997+
triggers)
4998+
4999+
Currently with Postgres-R, it is one database replicating all tables to
5000+
all servers in the group communication system. There are some ways
5001+
around
5002+
this by invoking the -r option when a SQL statement should be replicated,
5003+
and leaving the -r option off for non-replicated scenarios. IMHO this is
5004+
not a good solution.
5005+
5006+
A better solution will need to be implemented, which involves a
5007+
subscription table(s) with relation/server information. There are two
5008+
ideas for subscribing and receiving replicated data.
5009+
5010+
1) Receiver driven propagation - A simple solution where all
5011+
transactions are propagated and the receiving servers will reference
5012+
the subscription information before applying updates.
5013+
5014+
2) Sender driven propagation - A more optimal and complex solution
5015+
where servers do not receive any messages regarding data items for
5016+
which they have not subscribed
5017+
5018+
5019+
> > - what happens if one server is down? (or the network between) are
5020+
> > commits still possible
5021+
5022+
> No, updates are not possible if one target is not reachable,
5023+
5024+
AFAIK, Postgres-R can still replicate if one target is not reachable,
5025+
but only to the remaining servers ;).
5026+
5027+
There is a scenario that could arise if a server issues a lock
5028+
request then fails or goes off line. There is code that checks
5029+
for this condition, which needs to be merged with the branch we have.
5030+
5031+
> that would not be synchronous and would again need business rules
5032+
> to resolve conflicts.
5033+
5034+
Yes the failed server would not be synchronized, and getting this
5035+
failed server back in sync needs to be addressed.
5036+
5037+
> Allowing updates when a target is not reachable would require admin
5038+
> intervention.
5039+
5040+
In its current state yes, but our goal would be to eliminate this
5041+
requirement as well.
5042+
5043+
5044+
5045+
Darren
5046+
5047+
---------------------------(end of broadcast)---------------------------
5048+
TIP 3: if posting/reading through Usenet, please send an appropriate
5049+
subscribe-nomail command to [email protected] so that your
5050+
message can get through to the mailing list cleanly
5051+

0 commit comments

Comments
 (0)