vaiayand(at)gmail(dot)com writes:
> We investigated one issue and found the following:
> postgres is acquiring a lock on table when not in trancation during prepared
> ROLLBACK statement. It is releasing the acquired lock at end.
> but postgres should not get lock on a table when not in transaction. After
> acquiring any lock, if backend process dies (say SIGTERM signal), the
> postgres will be in lock-not-released state.
Thanks for the report. I believe I've fixed this.
regards, tom lane