On Tue, Feb 21, 2012 at 02:25:39PM +0000, Shaun McCloud wrote:
> Greg, I populated one table with 100000 bogus records and that 
> worked fine.  If I add a second table it stops working.
> 
> The setup is as follows.  We use ESRI replication technology to get 
> data from one ArcSDE instance into a PostgreSQL + PostGIS ArcSDE 
> instance on our server.  We then do a data only pg_dump on that 
> database and a psql load on our "live" database.  Slony is then 
> supposed to replicate the data out to the "live" database on our 
> other servers.  The problem is occurring on the last step :(

Yeah, can't think of what else it might be. Probably the only thing 
to do at this point, unless others on the list can think of things, 
is to edit one of the dumps to limit to a few rows, load it via 
psql, then check the slony tables (e.g. sl_log_1) to see if the 
triggers fired and how far it got. In other words, where is it 
breaking down? My guess is that the triggers are not populating 
the Slony tables for some reason, but there are other steps in which 
it could break down.

-- 
Greg Sabino Mullane greg at endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
Url : http://lists.slony.info/pipermail/slony1-general/attachments/20120223/26962561/attachment.pgp