简体   繁体   中英

Does postgresql release (advisory) locks after a DISCARD ALL; command?

Does postgresql release (advisory) locks after a DISCARD ALL; command?

It seems like it doesn't from this mail discussion I found . But I was wondering if anyone could tell me if this was changed or fixed in a new release since nov 2008 ?

https://www.postgresql.org/docs/current/static/sql-discard.html

Releases all temporary resources associated with the current session and resets the session to its initial state. Currently, this has the same effect as executing the following sequence of statements:

 SET SESSION AUTHORIZATION DEFAULT; RESET ALL; DEALLOCATE ALL; CLOSE ALL; UNLISTEN *; SELECT pg_advisory_unlock_all(); DISCARD PLANS; DISCARD SEQUENCES; DISCARD TEMP; 

supposedly?..

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM