Re: [ADMIN] Postgres log(pg_logs) have lots of message

That's just that some other process has some DML going on in the table that is supposed to be truncated. No lock, no truncate. HTH, Bambi. From: pgsql-admin-ow...@postgresql.org [mailto:pgsql-admin-ow...@postgresql.org] On Behalf Of Nik Tek Sent: Wednesday, April 10, 2013 4:58 PM To: pgsql-per

Re: [ADMIN] Pg max_connection

It is my understanding that connections consume 400b of memory apiece, and that the memory is only held while the process is active; so, if you drop 450 connections, your memory usage will drop about 200k. In this day and age, that doesn't mean a lot, but you should see mild performance improve

[ADMIN] Slony replication stopped replicating

Hi Gang! Slony replication has stopped replicating, and I'm not sure why, or how to get it replicating again. I have bounced Slony on the master and all the remote nodes, but no luck. Is there a Slony expert out there who can help point me in the right direction? Thanks! Bambi. This emai

Re: [ADMIN] Slony replication stopped replicating

On the prowl for the logs... meantime, here's the version info: $ slonik -v slonik version 2.1.0.b2 $ psql psql (9.0.4) From: Raghavendra [mailto:raghavendra@enterprisedb.com] Sent: Saturday, June 22, 2013 11:48 AM To: Bambi Bellows Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN]