On Thu, Feb 2, 2017 at 2:14 AM, Fujii Masao <masao.fu...@gmail.com> wrote: > The lwlock would be released when an exception occurs, so I don't think > that TRY-CATCH is necessary here. Or it's necessary for another reason?
+ PG_CATCH(); + { + LWLockRelease(LogicalRepLauncherLock); + PG_RE_THROW(); + } + PG_END_TRY(); Just to do that, a TRY/CATCH block looks like an overkill to me. Why not just call LWLockRelease in the ERROR and return code paths? -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers