Postgres Pro
Downloads
Home   >   mailing lists

Transaction-level advisory lock unlocking and transaction end - Mailing list pgsql-general

From Saimon Lim
Subject Transaction-level advisory lock unlocking and transaction end
Date
Msg-id CAOkVcQ6RcedhjBn2LGF9SmNdf9A+gi__kOgBcwr0L6DLdNOEFQ@mail.gmail.com
Whole thread Raw
Responses Re: Transaction-level advisory lock unlocking and transaction end  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Tree view
Hi,

I could not understand on the basis of documentation about transaction-level advisory lock:

> Transaction-level lock requests ... are automatically released at the end of the transaction ...

  So, what order will the use of transactions and unlock the lock?
The transaction would be applied at first and the lock would be unlocked after it or vice versa?
Or any order in this case is not guaranteed?

Thanks a lot for your help.
Saimon

pgsql-general by date:

Previous
From: sambsa
Date:
Subject: pgagent jobs Could not connect to the database !
Next
From: Thomas Kellerer
Date:
Subject: Re: can you have any idea about toast missing chunk issu resolution