Date: Thu, 28 Feb 2019 10:19:00 -0600
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
Message-ID: <20190228161900.GV28750@telsasoft.com>
References: <716d29c0713049e98cb80faff31db103@PCYINTPEXMU001.NEOPROD.EDF.FR>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <716d29c0713049e98cb80faff31db103@PCYINTPEXMU001.NEOPROD.EDF.FR>
User-Agent: Mutt/1.5.23 (2014-03-12)
Precedence: bulk

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