| From: | AI Rumman <rummandba(at)gmail(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Lock during insert statement |
| Date: | 2014-05-21 23:42:15 |
| Message-ID: | CAGoODpdkMeL3LvXNWk2ojagr=q16wT4-Abpi48-a2OuoAvXLKQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Got it.
Thanks.
Any special parameter to tune it? Like wal_buffers or shared_buffers?
On Wed, May 21, 2014 at 3:28 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> On Wed, May 21, 2014 at 3:14 PM, AI Rumman <rummandba(at)gmail(dot)com> wrote:
>
>> Could any one please tell me why my system is waiting to get lock for an
>> INSERT statement?
>>
>> 2014-05-21 07:52:49.965 PDT [9-1]LOG: process 31407 acquired
>> ExclusiveLock on extension of relation 429298276 of database 21497 after
>> 3219.963 ms
>>
>
> "on extension of relation" means that it needs to add 8KB to the end of
> the table. That it takes so long to obtain that locks suggests you have a
> some serious IO congestion.
>
> Cheers,
>
> Jeff
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G Johnston | 2014-05-21 23:50:05 | Re: Question regarding DEALLOCATE pdo_stmt_00000001 |
| Previous Message | Jeff Janes | 2014-05-21 22:28:28 | Re: Lock during insert statement |