Re: [HACKERS] proposal: lock_time for pg_stat_database

2015-01-21 Thread Pavel Stehule
Hi 2015-01-16 20:33 GMT+01:00 Jim Nasby : > On 1/16/15 12:30 PM, Pavel Stehule wrote: > >> >> >> 2015-01-16 19:24 GMT+01:00 Pavel Stehule > >: >> >> >> >> 2015-01-16 19:06 GMT+01:00 Jim Nasby > >: >> >> On 1/16/15 11:35

Re: [HACKERS] proposal: lock_time for pg_stat_database

2015-01-16 Thread Pavel Stehule
2015-01-16 20:33 GMT+01:00 Jim Nasby : > On 1/16/15 12:30 PM, Pavel Stehule wrote: > >> >> >> 2015-01-16 19:24 GMT+01:00 Pavel Stehule > >: >> >> >> >> 2015-01-16 19:06 GMT+01:00 Jim Nasby > >: >> >> On 1/16/15 11:35 AM,

Re: [HACKERS] proposal: lock_time for pg_stat_database

2015-01-16 Thread Jim Nasby
On 1/16/15 12:30 PM, Pavel Stehule wrote: 2015-01-16 19:24 GMT+01:00 Pavel Stehule mailto:pavel.steh...@gmail.com>>: 2015-01-16 19:06 GMT+01:00 Jim Nasby mailto:jim.na...@bluetreble.com>>: On 1/16/15 11:35 AM, Pavel Stehule wrote: 2015-01-16 18:23 GMT+01:00 Jim Na

Re: [HACKERS] proposal: lock_time for pg_stat_database

2015-01-16 Thread Pavel Stehule
2015-01-16 19:24 GMT+01:00 Pavel Stehule : > > > 2015-01-16 19:06 GMT+01:00 Jim Nasby : > >> On 1/16/15 11:35 AM, Pavel Stehule wrote: >> >>> >>> >>> 2015-01-16 18:23 GMT+01:00 Jim Nasby >> jim.na...@bluetreble.com>>: >>> >>> On 1/16/15 11:00 AM, Pavel Stehule wrote: >>> >>> Hi all, >>

Re: [HACKERS] proposal: lock_time for pg_stat_database

2015-01-16 Thread Pavel Stehule
2015-01-16 19:06 GMT+01:00 Jim Nasby : > On 1/16/15 11:35 AM, Pavel Stehule wrote: > >> >> >> 2015-01-16 18:23 GMT+01:00 Jim Nasby > jim.na...@bluetreble.com>>: >> >> On 1/16/15 11:00 AM, Pavel Stehule wrote: >> >> Hi all, >> >> some time ago, I proposed a lock time measurement

Re: [HACKERS] proposal: lock_time for pg_stat_database

2015-01-16 Thread Jim Nasby
On 1/16/15 11:35 AM, Pavel Stehule wrote: 2015-01-16 18:23 GMT+01:00 Jim Nasby mailto:jim.na...@bluetreble.com>>: On 1/16/15 11:00 AM, Pavel Stehule wrote: Hi all, some time ago, I proposed a lock time measurement related to query. A main issue was a method, how to show

Re: [HACKERS] proposal: lock_time for pg_stat_database

2015-01-16 Thread Pavel Stehule
2015-01-16 18:23 GMT+01:00 Jim Nasby : > On 1/16/15 11:00 AM, Pavel Stehule wrote: > >> Hi all, >> >> some time ago, I proposed a lock time measurement related to query. A >> main issue was a method, how to show this information. Today proposal is >> little bit simpler, but still useful. We can sh

Re: [HACKERS] proposal: lock_time for pg_stat_database

2015-01-16 Thread Jim Nasby
On 1/16/15 11:00 AM, Pavel Stehule wrote: Hi all, some time ago, I proposed a lock time measurement related to query. A main issue was a method, how to show this information. Today proposal is little bit simpler, but still useful. We can show a total lock time per database in pg_stat_database

[HACKERS] proposal: lock_time for pg_stat_database

2015-01-16 Thread Pavel Stehule
Hi all, some time ago, I proposed a lock time measurement related to query. A main issue was a method, how to show this information. Today proposal is little bit simpler, but still useful. We can show a total lock time per database in pg_stat_database statistics. High number can be signal about lo