Re: explain (verbose off, normalized) vs query planid

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: legrand legrand <legrand_legrand(at)hotmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: explain (verbose off, normalized) vs query planid
Date: 2018-05-14 18:45:01
Message-ID: CA+TgmoYzUjf=L39eBU0gzJgsW4VbWJEwHmjNEw5Pmp4GHO15aQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, May 12, 2018 at 6:07 PM, legrand legrand
<legrand_legrand(at)hotmail(dot)com> wrote:
> It seems natural (to me) to calculate a hash value based on the normalized
> plan text
> generated by
>
> explain (costs off, normalized)
> or maybe
> explain (costs off, verbose, normalized)

I would think it would be preferable to do it based on the node tree,
like pg_stat_statements does for query fingerprinting. But I guess it
might depend on what you want to do with it.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2018-05-14 18:55:45 Re: Allow COPY's 'text' format to output a header
Previous Message Garick Hamlin 2018-05-14 18:44:59 Re: Allow COPY's 'text' format to output a header