On 7/23/2004 5:01 PM, David Parker wrote:
> Sheesh....just need to get my eyes uncrossed....
> 
> Well, that's good to know.
> 
> Nobody has commented on the feasability/desirability of adding a
> partitioning capability to the replication as in my original
> question....

I do think that it has value. However, using "replication" to do in fact 
data transformation onto remote systems isn't what Slony was designed 
for in the first place. For now you only talk about splitting up the 
data into different tables, key based. But think it to the end, there 
you will want to merge this other tables fields when key based 
replicating to node 4, but munging those columns with some regular 
expression when replicating to node 6.

And it all leads to something Slony wasn't meant to do. With all this 
partial and segmented replicas you do not do failover, switchover or 
failback.


Jan

> 
> - DAP
> 
> -----Original Message-----
> From: David Fetter [mailto:david at fetter.org] 
> Sent: Friday, July 23, 2004 4:47 PM
> To: Dan Wright
> Cc: David Parker; slony1-general at gborg.postgresql.org
> Subject: Re: [Slony1-general] partitioning with replication
> 
> On Thu, Jul 22, 2004 at 06:15:55PM -0400, Dan Wright wrote:
> 
>> It sounds like you are doing the kind of thing that table inheritance 
>> is supposed to solve.  If you use inheritance in your DB tables, you 
>> could get exactly what you are asking for from slony right now.
> 
> Table inheritance is a Bad Thing(TM) in its current implementation.
> Please find attached an example of why this is so.
> 
> Cheers,
> D
> --
> David Fetter david at fetter.org http://fetter.org/
> phone: +1 510 893 6100   mobile: +1 415 235 3778
> 
> Remember to vote!
> 
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/slony1-general


-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck at Yahoo.com #