Hi, one thing I was trying to avoid was the connection overhead. For some reason this box has been configured to 1500 connections (sic), I have no immediate permission to install a pooler and obviously the overhead in creating new processes is one of the things that kill it... So I was trying to make it as painless as possible.
Cheerio Bèrto PS sorry Frank, you got mailed twice. I mistakenly hit a "reply only" the first time and it did not come to the list. On 20 March 2012 11:26, Frank Bax <f...@sympatico.ca> wrote: > On 03/20/12 06:14, Bèrto ëd Sèra wrote: > >> So as a dirty and quick hack to >> make sure our failure filter works I wanted to have an external process >> kill and relaunch the filter from cron each 30 minutes. >> >> Is there anyway I can mark the process running the filter, maybe using >> the update_process_title feature? I'd like to have something I can see >> from a ps command, grep for it and kill -15 it, without wasting our >> scarce resources on one more pg process to use info from pg_stat_activity. >> > > > Change your filter so it only runs once; not in a forever loop; then add > the filter to cron to run every minute. > > If this new filter continues to freeze; then use pkill to get rid of it. > Hopefully RHEL has a pkill command which works like (ps | grep | kill). > > -- > Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/**mailpref/pgsql-sql<http://www.postgresql.org/mailpref/pgsql-sql> > -- ============================== If Pac-Man had affected us as kids, we'd all be running around in a darkened room munching pills and listening to repetitive music.
