Hi Tom,
There must have been something like that because when we stopped and
started postgres again, it worked.
Thanks,
____________________________________________________________________
Brendan Duddridge | CTO | 403-277-5591 x24 | brendan@clickspace.com
ClickSpace Interactive Inc.
Suite L100, 239 - 10th Ave. SE
Calgary, AB T2G 0V9
http://www.clickspace.com
On May 5, 2006, at 2:06 PM, Tom Lane wrote:
> Brendan Duddridge <brendan@clickspace.com> writes:
>> They both have a click_count column that we update with "update
>> attribute set click_count = click_count + 1;" and the same for the
>> attribute_value table. Postgres is getting hung up on any transaction
>> that attempts to update the click_count. I've vacuum analyzed both
>> tables and that worked fine. Now I tried to reindex them and Postgres
>> is just locking up and never finishing. I had to cancel the reindex.
>
> I'd wonder about some open transaction with a weak lock on these
> tables. REINDEX needs exclusive lock, vacuum doesn't.
> Look in pg_locks ...
>
> regards, tom lane
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
