Hi Andrew,

thanks for your replies.

Unfortunately it seems that the load issue has something to do with slony because the queries are simple select statements and the database server is quite powerfull. Otherwise there would be the same performance issue when querying the slave.
The queries seem to hang for some reason, which does not seem to be a load issue on the database server.

Any idea of other causes?

Best regards
Burak

-------- Original-Nachricht --------
> Datum: Mon, 29 Jun 2009 09:27:53 -0400
> Von: Andrew Sullivan <ajs at crankycanuck.ca>
> An: Burak Bender <Burak.Bender at gmx.net>
> CC: ajs at crankycanuck.ca, slony1-general at lists.slony.info
> Betreff: Re: [Slony1-general] hanging slony replication

> On Mon, Jun 29, 2009 at 10:07:05AM +0200, Burak Bender wrote:
> 
> > If the script runs against a slony slave, everything is fine. But
> > against the master database, the replication as well as other
> > queries get very slow.
> 
> This sounds like a pure load issue -- you just have too many queries
> on your database.  Slony works by performing queries too, so it will
> be affected if the origin is overloaded.
> 
> A
> 
> -- 
> Andrew Sullivan
> ajs at crankycanuck.ca

-- 
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01