| From: | Joshua Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Emre Hasegeli <emre(dot)hasegeli(at)tart(dot)com(dot)tr> |
| Cc: | dba(at)tart(dot)com(dot)tr, pgsql-performance(at)postgresql(dot)org, pgsql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL 9.2.3 performance problem caused Exclusive locks |
| Date: | 2013-03-13 21:04:58 |
| Message-ID: | 978553984.25691.1363208698441.JavaMail.root@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
Emre,
> > LOG: process 4793 acquired ExclusiveLock on extension of relation
> > 305605 of database 16396 after 2348.675 ms
The reason you're seeing that message is that you have log_lock_waits turned on.
That message says that some process waited for 2.3 seconds to get a lock for expanding the size of relation 16396/305605, which is most likely an index. This is most likely due to changes in your application, or an increase in concurrent write activity.
--Josh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kirk Wythers | 2013-03-13 21:45:34 | big un stacking query - help save me from myself |
| Previous Message | Scott Marlowe | 2013-03-13 16:32:35 | Re: table spaces |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua Berkus | 2013-03-13 21:18:38 | Re: Risk of data corruption/loss? |
| Previous Message | David Boreham | 2013-03-13 20:16:16 | Re: New server setup |