On Mon, Dec 2, 2013 at 10:42 PM, Peter Eisentraut pete...@gmx.net wrote:
On 11/19/13, 11:30 PM, Peter Geoghegan wrote:
+1 from me.
That's +1 for *not* including this?
Right.
I agree with not including this.
If you're looking for more of those, here's another +1 for not including
On 11/19/13, 11:30 PM, Peter Geoghegan wrote:
+1 from me.
That's +1 for *not* including this?
Right.
I agree with not including this.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
On Mon, Nov 18, 2013 at 10:56 AM, Peter Geoghegan p...@heroku.com wrote:
On Mon, Nov 18, 2013 at 10:49 AM, Fujii Masao masao.fu...@gmail.com
wrote:
The same idea was proposed before but not committed because
Itagaki thought that pg_stat_statements view should report only raw
values.
On Tue, Nov 19, 2013 at 12:12 PM, Jeff Janes jeff.ja...@gmail.com wrote:
The same idea was proposed before but not committed because
Itagaki thought that pg_stat_statements view should report only raw
values.
Please read the following thread. I have the same feeling with him.
Anyway we
On 18 October 2013 13:35 KONDO Mitsumasa wrote:
Hi,
I submit improvement of pg_stat_statement usage patch in CF3.
In pg_stat_statement, I think buffer hit ratio is very important value.
However, it is difficult to calculate it, and it need complicated SQL.
This patch makes it more simple
(2013/11/18 20:16), Haribabu kommi wrote:
On 18 October 2013 13:35 KONDO Mitsumasa wrote:
This patch conflicts pg_stat_statement_min_max_exectime patch which I
submitted, and pg_stat_statement_min_max_exectime patch also adds new
columns which are min_time and max_time. So I'd like to change it
On Mon, Nov 18, 2013 at 8:36 PM, KONDO Mitsumasa
kondo.mitsum...@lab.ntt.co.jp wrote:
(2013/11/18 20:16), Haribabu kommi wrote:
On 18 October 2013 13:35 KONDO Mitsumasa wrote:
This patch conflicts pg_stat_statement_min_max_exectime patch which I
submitted, and
On Mon, Nov 18, 2013 at 10:49 AM, Fujii Masao masao.fu...@gmail.com wrote:
The same idea was proposed before but not committed because
Itagaki thought that pg_stat_statements view should report only raw values.
Please read the following thread. I have the same feeling with him.
Anyway we
(2013/11/19 3:56), Peter Geoghegan wrote:
On Mon, Nov 18, 2013 at 10:49 AM, Fujii Masao masao.fu...@gmail.com wrote:
The same idea was proposed before but not committed because
Itagaki thought that pg_stat_statements view should report only raw values.
Please read the following thread. I have
(2013/11/19 11:12), KONDO Mitsumasa wrote:
(2013/11/19 3:56), Peter Geoghegan wrote:
On Mon, Nov 18, 2013 at 10:49 AM, Fujii Masao masao.fu...@gmail.com wrote:
The same idea was proposed before but not committed because
Itagaki thought that pg_stat_statements view should report only raw
On Mon, Nov 18, 2013 at 6:12 PM, KONDO Mitsumasa
kondo.mitsum...@lab.ntt.co.jp wrote:
I confirmed that Itagaki-san and Mr Cerdic disscution. He said that raw
values be just simple. However, were his changes just simple? I cannot
understand his aesthetics sense and also you, too:-(
It's too
(2013/11/19 12:03), Peter Geoghegan wrote:
On Mon, Nov 18, 2013 at 6:12 PM, KONDO Mitsumasa
kondo.mitsum...@lab.ntt.co.jp wrote:
I confirmed that Itagaki-san and Mr Cerdic disscution. He said that raw
values be just simple. However, were his changes just simple? I cannot
understand his
On Mon, Nov 18, 2013 at 10:08 PM, KONDO Mitsumasa
kondo.mitsum...@lab.ntt.co.jp wrote:
I regret past decision of Itagaki-san's patch, and improvement might not be
possible. However, we can change it, if we get have logical reason to change
it.
I suppose so.
I don't think that the tool needs
13 matches
Mail list logo
