Re: BUG: pg_stat_statements query normalization issues with combined queries

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, craig(dot)ringer(at)2ndquadrant(dot)com, robertmhaas(at)gmail(dot)com, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: BUG: pg_stat_statements query normalization issues with combined queries
Date: 2017-01-12 19:02:10
Message-ID: alpine.DEB.2.20.1701121958580.3788@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> [...] it seems a lot cleaner to me.

I agree.

> [...] It's safe in backend-legal encodings.

Good:-)

> [...] The trouble for statements like EXPLAIN is that we replace the
> sub-statement during parse analysis, [...]

Ok. So Node* is fine to keep it generic.

--
Fabien.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2017-01-12 19:08:54 Re: BUG: pg_stat_statements query normalization issues with combined queries
Previous Message Stephen Frost 2017-01-12 19:01:21 Re: [PATCH] Rename pg_switch_xlog to pg_switch_wal