On Monday 16 July 2007 04:50:46 Al Rosenthal wrote:
> I have thought about firewalls and timeouts.  I just have two machines,
> sitting next to each other connected by a switch.  One has Vista, the other
> XP.  I tried running the slon engines on either one.  I also tried changing
> all of the IP settings available.  I also tried adding a linux machine and
> running the slon process on that machine.  In every case, the machine that
> is the slave failed after about 12 - 15 GB with a error 10055 (not enough
> buffer space or enough tcp buffers).  Also, the database I am trying to
> replicate is very simple.  One table, no indexes.  Even the table is
> simple. On serial column as primary key, the other is bytea data.
>
> Any suggestions?

Based on the descriptions you have given, I'm fairly convinced that this is 
not a slony problem, but rather a PostgreSQL more specificaly a Windows 
problem,   During the subscribe phase of the replication slony basicly mimics 
pg_dump | psql.   The fact that you've moved the slon processes to a linux 
machine yet still get this error,  pretty much confirms this for me.  Some 
googeling around leads me to see the following: 
http://archives.postgresql.org/pgsql-ports/2005-11/msg00000.php  Which sounds 
like it could be exactly what you are experiencing.

What version of PostgreSQL are we dealing with here?


>
> Al
>
> >> What I still can not do is replicate a 22 GB database.  My initial
> >> trials all failed after about 12 to 15 GB with an error 10055 in
> >> the logs.  According to windows knowlegebase, this is because of a
> >> lack of TCP buffers.  I followed microsoft's advice and edited the
> >> registry and changed such things as the MaxUserPort and
> >> TCPTimedWaitDelay and TcpNumConnections to their maximums.
> >
> >I wonder if you're timing out.  What I know about Windows any more is
> >very close to zero, but my suspicion is that you might be building an
> >index or something that is taking a long time.  You will have issued
> >a command, and then you wait for it to complete.  If the time to
> >complete is longer than the time your settings are willing to wait,
> >then you can get in trouble.  (This could also be due to an
> >intermediate firewall deciding that your session is "idle".)
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
-- 


Darcy Buskermolen
The PostgreSQL company, Command Prompt Inc.
http://www.commandprompt.com/