Re: ANALYZE locks pg_listener in EXCLUSIVE for long

From: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ANALYZE locks pg_listener in EXCLUSIVE for long
Date: 2004-05-03 09:33:40
Message-ID: 6.1.0.6.0.20040503193226.048ae508@203.8.195.10
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At 06:21 PM 3/05/2004, Philip Warner wrote:
>'tuple concurrently updated'

I lied. The database DO NOT logs show the same error in each case where a
long delay has occurred. It happens sometimes; recent process logs do show
the 'async_notify waiting' status, however.

I'll try not to send any more emails until someone responds ;-)

----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 03 5330 3172 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp.mit.edu:11371 |/

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2004-05-03 09:39:08 Aclitem "high level description"
Previous Message Philip Warner 2004-05-03 09:25:27 Re: ANALYZE locks pg_listener in EXCLUSIVE for long