On Thu, May 8, 2014 at 10:41 AM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Thu, May 8, 2014 at 2:31 AM, Jaime Casanova <jaime@2ndquadrant.com> wrote:
>> On Wed, May 7, 2014 at 10:52 PM, Amit Kapila <amit.kapila16@gmail.com> wrote:
>>> On Thu, May 8, 2014 at 5:30 AM, Jaime Casanova <jaime@2ndquadrant.com> wrote:
>>>> Hi,
>>>>
>>>> This patch implements $subject only when ANALYZE and VERBOSE are on.
>>>> I made it that way because for years nobody seemed interested in this
>>>> info (at least no one did it) so i decided that maybe is to much
>>>> information for most people (actually btree indexes are normally very
>>>> fast).
>>>
>>>
> I would have expected the information about index maintenance times to
> be associated with the Insert node, not the plan overall. IIUC, you
> could have more than one such node if, for example, there are
> writeable CTEs involved.
>
i followed how trigger info is showed in explain. I can try to change
it, if that is what most people prefer.
QUERY PLAN
---------------------------------------------------------------------------------------------------------------------Insert
onpgbench_accounts (actual time=0.249..0.249 rows=0 loops=1) CTE results -> Insert on pgbench_accounts
pgbench_accounts_1(actual
time=0.152..0.159 rows=1 loops=1) -> Result (actual time=0.003..0.004 rows=1 loops=1) -> CTE Scan on
results(actual time=0.165..0.174 rows=1 loops=1)Trigger trg1 on pgbench_accounts: time=0.033 calls=1Trigger trg1 on
pgbench_accounts:time=0.059 calls=1Total runtime: 0.377 ms
(8 rows)
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
Phone: +593 4 5107566 Cell: +593 987171157