Re: pg_stat_statements query jumbling question

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Satoshi Nagayasu <snaga(at)uptime(dot)jp>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_stat_statements query jumbling question
Date: 2015-09-01 03:36:51
Message-ID: CAM3SWZRN_Mhyk0T+UUOec9ac7Vz8PwKDGEo8OTbRmGq-9b9WOA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Aug 31, 2015 at 8:32 PM, Satoshi Nagayasu <snaga(at)uptime(dot)jp> wrote:
> Why don't we use relation name (with looking up the catalog)
> on query jumbling? For performance reason?

I think that there is a good case for preferring this behavior. While
it is a little confusing that pg_stat_statements does not change the
representative query string, renaming a table does not make it a
substantively different table.

There is, IIRC, one case where a string is jumbled directly (CTE
name). It's usually not the right thing, IMV.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2015-09-01 03:57:25 perlcritic
Previous Message Satoshi Nagayasu 2015-09-01 03:32:24 pg_stat_statements query jumbling question