hi slony-folks--

I've got a slony-I 2.0.4 system replicating between two psql databases.

If i run pg_top on the origin node, i regularly see ~25% CPU usage in a
fetch command that appears to be:

 fetch 500 from LOG;

(i get this query string from "SELECT * FROM pg_stat_activity;")  The pg
user associated with this query is the user account used by the slon
process.

In addition to this problem on the origin node, i see a long-standing
"idle in transaction" process via pg_top on the subscribed node,

I found this entry in the FAQ:

 http://slony.info/documentation/faq.html#AEN5103

But i'm not clear what to do to improve the situation.  Can you suggest
next steps that would be useful?

My frontend application isn't using connection pooling -- it's a
perl-based fcgi script.

I would appreciate any advice!

Regards,

	--dkg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1030 bytes
Desc: OpenPGP digital signature
Url : http://lists.slony.info/pipermail/slony1-general/attachments/20110819/ef39171f/attachment.pgp