It seems likely that something other than slony is causing your
problems, but hard to know what.  Maybe the network or database
locking.  Some suggestions:

Use the released version of 2.0.4.  I don't know if anything changed
or not, but always best to use released versions where possible.

Before replicating anything, double check that postgres is working as
rapidly as you would expect, both master and slave, accessed from both
servers.

Double check the network comms between master and slave databases.


Then switch replication on and see what happens.



--
Ian.


On Mon, Jun 28, 2010 at 8:36 AM, Sachin Kumar <Sachin.Ku at globallogic.com> wrote:
> Hi,
>
>
>
> We are using postgresql-8.4.0 on 64-bit Linux machine (open-SUSE 11.x). It’s
> a master/slave deployment & slony-2.0.4.rc2 is used for DB replication on
> the slave box.
>
>
>
> At times we have observed that postgres stops responding, even couldn’t
> fetch the number of entries in a particular table. One such instance happens
> when we execute the
>
> following steps:
>
> -         Add few lakh entries (~ 20) to table X on the master DB.
>
> -         After addition, slony starts replication on the slave DB. It takes
> several minutes (~25 mins) for replication to finish.
>
> -         During this time (while replication is in progress), postgres
> stops responding, i.e. we couldn’t even fetch the number of entries in any
> table (X, Y, etc).
>
>
>
> Can you please let us know:
>
> -         Why it takes so long for replication? How it can be improved?
>
> -         What could be reason for postgres to stop responding?
>
>
>
>
>
> Thanks in advance!!
>
>
>
> Regards,
>
> Sachin
>
>
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
>
>