Kyotaro HORIGUCHI wrote:
Hi, I saw this patch has been moved into committed patches but
only the first part (0001_..) for the core is committed as of
32001ab but the rest for extension side seem not to have been
committed.
Would you mind taking a look on that, Álvaro?
Yep, pushed.
--
Hello,
Kyotaro HORIGUCHI wrote:
Hi, I saw this patch has been moved into committed patches but
only the first part (0001_..) for the core is committed as of
32001ab but the rest for extension side seem not to have been
committed.
Would you mind taking a look on that, Álvaro?
Yep,
Hi, I saw this patch has been moved into committed patches but
only the first part (0001_..) for the core is committed as of
32001ab but the rest for extension side seem not to have been
committed.
Would you mind taking a look on that, Álvaro?
regards,
At Wed, 22 Jan 2014 17:28:27 +0900,
Hello, I came back with doc patch and revised 0002 patch.
I think documentation is the only thing that stops this patch to be
commitable... can you add it?
Agreed. I have pushed patch 0001 for now.
Thank you, I'll put it sooner.
I found the default setting for log_triggers was
Hello,
This patch consists of two parts,
0001_expose_explain_triggers_v1_20140114.patch
0002_auto_explain_triggers_v1_20140114.patch
Documentation will be added later..
I think documentation is the only thing that stops this patch to be
commitable... can you add it?
On Tue, Jan 14, 2014 at 4:25 AM, Kyotaro HORIGUCHI
horiguchi.kyot...@lab.ntt.co.jp wrote:
This patch consists of two parts,
0001_expose_explain_triggers_v1_20140114.patch
Expose the code to print out trigger information currently
hidden in ExplainOnePlan().
Jaime Casanova wrote:
On Tue, Jan 14, 2014 at 4:25 AM, Kyotaro HORIGUCHI
horiguchi.kyot...@lab.ntt.co.jp wrote:
This patch consists of two parts,
0001_expose_explain_triggers_v1_20140114.patch
0002_auto_explain_triggers_v1_20140114.patch
Documentation will be added later..
I
Hello,
Now explain can show trigger statistics (from when?).
=# create table t (a int, b int);
=# create or replace function hoge() returns trigger as 'begin new.b = new.a;
return new; end;' language plpgsql;
=# create trigger ins_hoge before insert or update on t for each row execute
