Re: Nonexistent pid in pg_locks

Joe Uhl <joeuhl(at)gmail(dot)com> writes:
> I had to bounce an OpenMQ broker this morning (this database is the DB
> for an OpenMQ HA setup) and couldn't get it to reconnect to postgres.
> On inspecting the database I found dozens of vacuum processes waiting
> (I have a cron job that vacuums each night) and chewing up connection
> slots. Killing those left a few autovacuum worker process waiting.
> Killing those left just this one orphaned pid apparently holding a
> lock. Assumably they were all waiting on the lock "held" by 10453.

What exactly did you do to "kill" those processes? Do you remember
whether any of them happened to have PID 10453?

> Is there any way for me to clear that orphaned entry out of pg_locks?

Restarting the database should take care of this, I think.

regards, tom lane