pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Justin Pryzby <pryzby@telsasoft.com>
To: ROS Didier <didier.ros@edf.fr>
Cc: pgsql-performance@postgresql.org
Subject: Re: How to get the content of Bind variables
Date: Thu, 28 Feb 2019 10:19:00 -0600
Message-ID: <20190228161900.GV28750@telsasoft.com> (raw)
In-Reply-To: <716d29c0713049e98cb80faff31db103@PCYINTPEXMU001.NEOPROD.EDF.FR>
References: <716d29c0713049e98cb80faff31db103@PCYINTPEXMU001.NEOPROD.EDF.FR>

On Thu, Feb 28, 2019 at 12:21:56PM +0000, ROS Didier wrote:
> Statement: update t_shared_liste_valeurs set deletion_date=$1, deletion_login=$2, modification_date=$3, modification_login=$4, administrable=$5, libelle=$6, niveau=$7 where code=$8
> 
> รจ how to get the content of the bind variables ?

What is your setting of log_error_verbosity ?
https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-ERROR-VERBOSITY

Also, I recommend using CSV logs, since they're easier to import into the DB
and then easier to parse.
https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-ERROR-VERBOSITY

Also, note that you can either set log_min_duration_statement=0, which logs all
statement durations, and associated statements (if they haven't been previously
logged).

Or, you can set log_statement=all, which logs all statements (but duration is
only logged according to log_min_duration_statement).

Justin




view thread (18+ messages)  latest in thread

Message-ID: <20190228161900.GV28750@telsasoft.com>
Permalink:  ../20190228161900.GV28750@telsasoft.com/
Also on:    postgresql.org/message-id/20190228161900.GV28750@telsasoft.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: pryzby@telsasoft.com, didier.ros@edf.fr
  Subject: Re: How to get the content of Bind variables
  In-Reply-To: <20190228161900.GV28750@telsasoft.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox