Re: Fwd: Regarding pg_stat_statements

From: Matthew McGuire <mmcguire(at)parchment(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Fwd: Regarding pg_stat_statements
Date: 2015-03-13 15:14:15
Message-ID: CAFWbG9pu0F0Qm4ocvRYvMrLZA51joendxBA7+9ZohfqCeyDGHQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

You can set log_min_duration_statement = 0 to log every statement.

On Fri, Mar 13, 2015 at 3:38 AM, Sreerama Manoj <manoj(dot)sreerama973(at)gmail(dot)com
> wrote:

>
> Hi,
> As we know that "pg_stat_statements" will monitor the queries after
> normalizing the queries(Removes the values present in query). I want to
> know is there a way to store those normalized values because I want to
> check the type of data(values) ,range of data that is being hit to the
> database. I am using Postgres 9.4
>
>

--
*Matt McGuire *| Manager, Data Management
*mmcguire(at)parchment(dot)com <mmcguire(at)parchment(dot)com>*
direct

*916.367.6868*

*ext. 1633 | mobile 916.549.9809*

*3000 Lava Ridge Court, Suite 210 Roseville, CA 95661*

*Parchment *| Turn Credentials into Opportunities
www.parchment.com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ronan Dunklau 2015-03-13 16:20:09 Re: Regarding pg_stat_statements
Previous Message Adrian Klaver 2015-03-13 14:35:27 Re: DB Connections

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2015-03-13 15:26:05 pg_dump quietly ignore missing tables - is it bug?
Previous Message Kevin Grittner 2015-03-13 15:08:25 Re: Reduce pinning in btree indexes