From: | Mason Hale <masonhale(at)gmail(dot)com> |
---|---|
To: | pgsql-general General <pgsql-general(at)postgresql(dot)org> |
Subject: | waiting for ExclusiveLock on extension of relation |
Date: | 2009-06-01 23:13:31 |
Message-ID: | 8bca3aa10906011613l8ac2423h8153bbd2513dc159@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello --
I'm seeing some odd warning in my postgres (8.3.6) logs.
2009-06-01 20:01:59 UTC (10.11.199.136)LOG: process 7070 still
waiting for ExclusiveLock on extension of relation 43911 of database
43623 after 1001.240 ms
2009-06-01 20:01:59 UTC (10.11.199.136)LOG: process 7070 acquired
ExclusiveLock on extension of relation 43911 of database 43623 after
1335.801 ms
2009-06-01 20:02:29 UTC (10.11.199.136)LOG: process 6971 still
waiting for ExclusiveLock on extension of relation 43862 of database
43623 after 1001.076 ms
2009-06-01 20:02:30 UTC (10.11.199.136)LOG: process 6971 acquired
ExclusiveLock on extension of relation 43862 of database 43623 after
1979.106 ms
Googling around I've seen mention that this sort of lock is indicative
of waiting for a new btree index page to be created on disk (see:
http://archives.postgresql.org/pgsql-hackers/2004-11/msg00314.php)
Yet I'm surprised this is taking > 1 full second with some frequency.
My questions:
(1) how worried should I be about this?
(2) what can/should I do to alleviate/prevent this issue?
thanks in advance,
- Mason
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-06-01 23:16:32 | Re: waiting for ExclusiveLock on extension of relation |
Previous Message | Tom Lane | 2009-06-01 22:48:58 | Re: pl/pgsql FOUND variables and RULES |