Postgres Pro
Downloads
Home   >   mailing lists

Re: Code paths where LWLock should be released on failure - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Code paths where LWLock should be released on failure
Date
Msg-id 18073.1429767976@sss.pgh.pa.us
Whole thread Raw
In response to Code paths where LWLock should be released on failure  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Code paths where LWLock should be released on failure
List pgsql-hackers
Tree view 
Michael Paquier <michael.paquier@gmail.com> writes:
> After looking at bug #13128, I have been looking at the code around
> LWLockAcquire/Release to see if there are similar issues elsewhere.
> Here are my findings:

IIRC, we automatically release all LWLocks at the start of error recovery,
so I rather doubt that any of this is necessary.
        regards, tom lane

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Code paths where LWLock should be released on failure
Next
From: Michael Paquier
Date:
Subject: Re: Bogus WAL segments archived after promotion