Re: SQL history.

From: Syed Asim Shah <asim(dot)shah(at)telenor(dot)com(dot)pk>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: SQL history.
Date: 2017-10-30 07:33:18
Message-ID: C35F307BE15BEA4585014E7B3753CC96FDFB763C15@ISB-EXMB-CLUS.telenor.com.pk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Dear David,

Thanks for the update. What will be the performance impact after enabling “log_statement” feature (on high transactional databases).

BR!
Asim Shah.

From: David G. Johnston [mailto:david(dot)g(dot)johnston(at)gmail(dot)com]
Sent: Friday, October 27, 2017 6:59 PM
To: Syed Asim Shah
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] SQL history.

On Fri, Oct 27, 2017 at 3:08 AM, Syed Asim Shah <asim(dot)shah(at)telenor(dot)com(dot)pk<mailto:asim(dot)shah(at)telenor(dot)com(dot)pk>> wrote:
Dear Team,

We are having POSGRESQL version 9.6 installed on OS version Linux REDHAT 7.2. How we can fetch historical SQL executions trend of last 24 hours.

​See​

​https://www.postgresql.org/docs/9.6/static/pgstatstatements.html

and

​https://www.postgresql.org/docs/9.6/static/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHAT (log_statement)

For possibilities. Neither are installed/configured/enabled by default to capture the information you seek.

David J.

________________________________
This e-mail has been scanned for viruses by Forefront Protection @ Telenor Pakistan.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Ferrell, Denise D CTR NSWCDD, H11 2017-10-30 12:16:02 Re: [Non-DoD Source] Re: Database Error
Previous Message Vianello, Daniel A 2017-10-27 14:59:16 Re: SQL history.