>
> I have had some 'idle in transaction' connections hanging out from time to time that have caused issues on this
machinethat could explain the above perma-bloat. That is one thing that could affect the case reported here as well.
Theworst thing about those, is you can't even force kill those connections from within postgres (pg_cancel_backend
doesn'twork on them, and killing them via the OS bounces postgres ...) so you have to hunt down the offending client.
>
Ooh, I just noticed pg_terminate_backend() ... maybe this will let me kill annoying idle in transaction clients. I
guessthis arrived in 8.4? Hopefully this won't cause the whole thing to bounce and close all other backends....
>
>> regards, tom lane
>>
>> --
>> Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-performance
>
>
> --
> Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
