[EMAIL PROTECTED] wrote:
> DECLARE
> varUnlocked boolean;
> BEGIN
> varUnlocked:= pg_try_advisory_lock( 783264760123456 ); -- Try to lock function
> IF not varUnlocked THEN return NULL; END IF; -- exit if locking is
> unsucessfull
>
> WRONG QUERY HERE WHICH INTERRUPT EXECUTION
>
> varUnlocked:
<[EMAIL PROTECTED]> writes:
> EXPECTED: Pg must unlock if function execution failed
This is not a bug; it is the intended and documented behavior
of advisory locks.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your
