Chris,
pg_advisory_unlock (along with the other functions in that family) works
on a set of mythical objects with no actual meaning beyond what the
database administrator chooses to give them.
Thank you for your excellent description. I have never used the advisory
lock functionality that Pos
On Fri, Feb 10, 2012 at 2:35 AM, Gary Chambers wrote:
> Is it possible that
> Postgres is not receiving a meaningful response with respect to
> ExclusiveLock locking (i.e. unable to really obtain an ExclusiveLock) due to
> VM "disk" residing on an NFS mount?
pg_advisory_unlock (along with the oth
Chris (et al.),
Thanks for the reply. I have not replied sooner because I was hoping to get
some more feedback from the list.
I have a recently-migrated Pg cluster running 8.4.7 on Red Hat Enterprise
Linux Client release 5.7 (Tikanga) in a VMware VM that is logging the
subject warning. The ap
On Sat, Feb 4, 2012 at 8:27 AM, Gary Chambers wrote:
> All,
>
> I have a recently-migrated Pg cluster running 8.4.7 on Red Hat Enterprise
> Linux Client release 5.7 (Tikanga) in a VMware VM that is logging the
> subject warning. The application code is considerably old (deployed back in
> the 7.4
All,
I have a recently-migrated Pg cluster running 8.4.7 on Red Hat Enterprise
Linux Client release 5.7 (Tikanga) in a VMware VM that is logging the
subject warning. The application code is considerably old (deployed back in
the 7.4 days, I believe) and the message is preceded by a call to selec
