Re: New sessions on a database to be dropped consume 100% cpu

Feike Steenbergen <feikesteenbergen(at)gmail(dot)com> writes:
> While dropping a database, I was unable to do so because of a connected
> session. I used pg_terminate_backend to try to get rid of the session,
> however it is unkillable (from postgres).

The stack trace shows that it's stuck trying to make index entries for
some pg_depend additions. I'm wondering if one of the indexes for
pg_depend is corrupt (infinite loop of page right-links, say).
If you could install amcheck and see what it thinks about those indexes,
that would be interesting.

Of course, if you're just wishing you could get rid of the database,
you could forcibly kill those processes and move on.

regards, tom lane