| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | T <kurt023(at)hotmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Is it possible that session lock is not released |
| Date: | 2013-12-12 04:12:33 |
| Message-ID: | 22983.1386821553@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
T <kurt023(at)hotmail(dot)com> writes:
> Now transaction goes to default state, then this backend is killed or some FATAL error happens,
> AbortOutOfAnyTransaction() in ShutdownPostgres() will do nothing since transaction is in default
> state, and session lock on heaprelid is still held after ShutdownPostgres(), so subsequent operations
> could be blocked by this session lock.
This would only be an issue if we were to accept interrupts between the
CommitTransactionCommand() and StartTransactionCommand() steps ... which
we don't. I'll admit it's a tad on the fragile side but I don't see a
bug.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dev Kumkar | 2013-12-12 07:04:39 | Re: Case sensitivity |
| Previous Message | Chris Travers | 2013-12-12 04:07:22 | Re: postgresql.org inconsistent (Re: PG replication across DataCenters) |