Shreeyansh,
that will be an overhead for the database, can we get information via query ?
Regards,
Anjul TYAGI
ü Go Green
------ Original Message ------
From: "Shreeyansh Dba" <shreeyansh2014@xxxxxxxxx>
To: "Anjul Tyagi" <anjul@xxxxxxxxxxxxxxxx>
Cc: "pgsql-admin" <pgsql-admin@xxxxxxxxxxxxxx>
Sent: 01-10-2018 15:30:48
Subject: Re: Blocking Alert
Hi Anjul,
You can use log_statement = all in postgresql.conf if you want full parameter logging.
Another option is to set log_min_duration_statement = 0 to use with pgBadger to get the actual parameter value in place of $1 and $2.On Mon, Oct 1, 2018 at 11:32 AM Anjul Tyagi <anjul@xxxxxxxxxxxxxxxx> wrote:Hi All,we recently implement the blocking alert in our production server. However whenever we receive the blocking alert, we need th actual parameters value to figure out the issues. Can you please help up to get the actual parameter value in place of $1 and $2.blocked_pid | blocked_user | blocked_duration | blocking_pid | blocking_user | blocking_duration | blocked_statement | blocking_statement
-------------+--------------+------------------+--------------+---------------+-------------------+-------------------------------------------------------------------------+-------------------------------------------------------------------------
21961 | ssusers | 00:00:03.729771 | 15928 | ssusers | 00:00:24.207317 | select * from get_updated_doc_list($1,XML($2)) as result | select * from get_updated_doc_list($1,XML($2)) as result
(1 row)Regards,
Anjul TYAGI
ü Go Green
