Re: Schedule for 8.1 feature freeze

> I realise there probably won't be time to fix pg_terminate_backend, or
> convince people that it offers the admin the lesser of two evils (my
> limited understanding being that there is a chance of it not clearing
> some locks, vs, having to shut down the whole server to kill a single
> connection) - can we at least get the other functions applied?

Not clearing those locks frequently results in a "Lock Table corruption"
message and panic at some unknown point in the future, and is probably
not something we want to encourage.

It looks really bad when it happens hours or days after the connection
was killed because the user isn't going to associate those two actions.

This is a feature I'm really looking forward too, but it's not ready for
general consumption yet.

--