Found the archive entry, and I think you did a very good job of =

convincing me to NOT use your script :)


To quote:

PLEASE READ THE DOCS before you use this.  This thing is _dangerous_. =

It's intended to solve a specific problem.  It is _really really not_
intended to solve generic load-and-replace issues.  Even more, there
are plenty of places where it can completely break replication in
your Slony cluster on a table.  I strongly suggest you use this on a
table that is isolated in its own set.  Even there, things might
break.

Given that introduction, would any sane person even consider it?

Cheers,
jason


Andrew Sullivan wrote:
> On Sun, Sep 16, 2007 at 08:45:54PM -0700, Jason L. Buberel wrote:
>   =

>> The problem appears to have been caused by the presence of =

>> 'pg_bulkload'. There seems to be some essential conflict between that =

>>     =

>
> What is pg_bulkload?  In any case. . .
>
>   =

>> utility and slony. Although I cannot be 100% sure, these are the steps I =

>>     =

>
> I should think so, since Slony doesn't allow you to do that sort of
> thing on a replica.  I sent a Perl script to the list some time ago
> that provides a Slony-compatible bulk loader.  Check the archives.
>
> A
>
>   =

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20070917/=
a39c5e55/attachment.htm