Re: Limiting the amount of data in a variable when logging slow queries

From: Brett Delle Grazie <brett(dot)dellegrazie(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Limiting the amount of data in a variable when logging slow queries
Date: 2017-04-23 17:23:50
Message-ID: CACLD0=5er2eKQc9H82CTSQ4HmBJsDfner2TDH0c=3vDPLOLR0A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 21 April 2017 at 12:13, Brett Delle Grazie <brett(dot)dellegrazie(at)gmail(dot)com>
wrote:

> Hi,
>
> We've enabled the slow query log and have a particular query that is
> executing an insert against a table containing a binary array column.
>
> Given the content being stored is upwards of 100MB+ this leads to very
> long log messages for the slow query log.
>
> Is there a way of having the slow query log only output the first 'n'
> bytes of a byte array and/or exempting this particular insert?
>

I believe I might have solved this by using (testing now):

log_error_verbosity = TERSE

However this is a rather blunt instrument. So if anyone has any better
suggestions I'm all ears.

Thanks,

--
Kind regards,

Brett Delle Grazie

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Guyren Howe 2017-04-23 17:24:33 Re: Does a view not define a composite type?
Previous Message Guyren Howe 2017-04-23 17:12:54 Does a view not define a composite type?