Re: [GENERAL] lock contention, need profiling idea

2014-07-01 Thread Merlin Moncure
On Tue, Jul 1, 2014 at 2:28 PM, Jeff Janes wrote: >> You should have a look at pg_stat_activity, pg_prepared_xacts and pg_locks >> to get more information about the transactions running and the locks being >> taken. > > In 9.4, the log message will also include info on the blocking > process, not

Re: [GENERAL] lock contention, need profiling idea

2014-07-01 Thread Jeff Janes
On Mon, Jun 30, 2014 at 5:06 PM, Michael Paquier wrote: > On Tue, Jul 1, 2014 at 7:36 AM, AI Rumman wrote: >> >> I see lots of similar log message at a certain time in a day on Postgresql >> 9,.1: >> >> LOG: process 18855 still waiting for ShareLock on transaction 2856146023 >> after 1001.209 ms

Re: [GENERAL] lock contention, need profiling idea

2014-07-01 Thread Merlin Moncure
On Mon, Jun 30, 2014 at 5:36 PM, AI Rumman wrote: > I see lots of similar log message at a certain time in a day on Postgresql > 9,.1: > > LOG: process 18855 still waiting for ShareLock on transaction 2856146023 > after 1001.209 ms > STATEMENT: UPDATE table1 SET time = $1 WHERE id = $2 > > The t

Re: [GENERAL] lock contention, need profiling idea

2014-07-01 Thread AI Rumman
There was no CREATE INDEX command running on the host. On Mon, Jun 30, 2014 at 5:06 PM, Michael Paquier wrote: > > > > On Tue, Jul 1, 2014 at 7:36 AM, AI Rumman wrote: > >> I see lots of similar log message at a certain time in a day on >> Postgresql 9,.1: >> >> LOG: process 18855 still waiti

Re: [GENERAL] lock contention, need profiling idea

2014-06-30 Thread Michael Paquier
On Tue, Jul 1, 2014 at 7:36 AM, AI Rumman wrote: > I see lots of similar log message at a certain time in a day on Postgresql > 9,.1: > > LOG: process 18855 still waiting for ShareLock on transaction 2856146023 > after 1001.209 ms > STATEMENT: UPDATE table1 SET time = $1 WHERE id = $2 > > The t