Re: Vacuum as "easily obtained" locks - Mailing list pgsql-general

From Jerry Sievers
Subject Re: Vacuum as "easily obtained" locks
Date
Msg-id 8739hictqd.fsf@comcast.net
Whole thread Raw
In response to Re: Vacuum as "easily obtained" locks  (Michael Graham <mgraham@bloxx.com>)
List pgsql-general
Michael Graham <mgraham@bloxx.com> writes:

> On Wed, 2011-08-03 at 10:17 -0400, Tom Lane wrote:
>
>> Michael Graham <mgraham@bloxx.com> writes:
>> > Would my applications
>> > constant polling of the queue mean that the lock could not be easily
>> > obtained?
>>
>> Very possible, depending on what duty cycle is involved there.
>
> Hmm.  The clients aren't that aggressive, especially when they failed to
> find data on a previous select, there are 4 clients, they each poll
> every 10 seconds and the select runs in <1ms.
>
> It might be worth noting that they don't ever disconnect from the
> server, but I assume that is not an issue for getting the
> AccessExclusiveLock on the table?

You are certain that those clients do these quick select as
auto-commit?

What does select current_query from pg_stat_activity say?

--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres.consulting@comcast.net
p: 305.321.1144

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Vacuum as "easily obtained" locks
Next
From: Eduardo Morras
Date:
Subject: Re: Vacuum as "easily obtained" locks