Re: is pg_advisory_lock() suitable for long runs

On Sat, Mar 31, 2018 at 1:49 PM, Radoslav Nedyalkov wrote: > Hi all, > it's very simple and intuitive case but let me describe first. > 1. session 1 calls pg_advisory_lock(1234) and succeeds. > 2. session 2 calls pg_advisory_lock(1234) and stops on waiting. > All fine BUT pid for session2 appears

is pg_advisory_lock() suitable for long runs

Hi all, it's very simple and intuitive case but let me describe first. 1. session 1 calls pg_advisory_lock(1234) and succeeds. 2. session 2 calls pg_advisory_lock(1234) and stops on waiting. All fine BUT pid for session2 appears already with backend_xmin in pg_stat_activity which means vacuum won't