Re: Trigger information for auto_explain.

From: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
To: alvherre(at)2ndquadrant(dot)com
Cc: jaime(at)2ndquadrant(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Trigger information for auto_explain.
Date: 2014-02-25 09:20:18
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

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

Would you mind taking a look on that, Álvaro?


At Wed, 22 Jan 2014 17:28:27 +0900, Kyotaro HORIGUCHI wrote
me> Hello, I came back with doc patch and revised 0002 patch.
me> > > > I think documentation is the only thing that stops this patch to be
me> > > > commitable... can you add it?
me> > >
me> > > Agreed. I have pushed patch 0001 for now.
me> >
me> > Thank you, I'll put it sooner.
me> I found the default setting for log_triggers was true in the last
me> patch while writing doc but it's better be false ragarding
me> backward compatibility. The 0002 patch attached has been changed
me> there.
me> - 0002_auto_explain_triggers_v2_20140122.patch
me> default value for log_triggers from 'true' to 'false'. As added
me> documents says.
me> - 0003_auto_explain_triggers_doc_v1_20140122.patch
me> documentation.

Kyotaro Horiguchi
NTT Open Source Software Center

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2014-02-25 09:25:17 Re: Dump pageinspect to 1.2: page_header with pg_lsn datatype
Previous Message Ashutosh Bapat 2014-02-25 08:59:18 Re: Custom Scan APIs (Re: Custom Plan node)