Sv: RE: Transactions

From: Andreas Joseph Krogh <andreas(at)visena(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Sv: RE: Transactions
Date: 2019-04-09 10:07:24
Message-ID: VisenaEmail.7.5f9cc306e7db9b59.16a018e2ee0@tc7-visena
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

På tirsdag 09. april 2019 kl. 11:56:28, skrev Karl Martin Skoldebrand <
KS0C77263(at)TechMahindra(dot)com <mailto:KS0C77263(at)TechMahindra(dot)com>>:
How much impact on performance and disk space would this or

set log_min_duration_statement=0

have?

I have no idea as to how common this is, or when it happens, so it would need
to run until this reported again (or some reasonable time if it doesn’t happen).
Well, the answer here is of course "it depends"... If you have lots of
activity the logs will fill up quite quickly, but you can easily test this in
production and just turn off logging again by setting it to 'none' and reload
settings (no need to restart). You can also only log modifications by setting
log_statement = 'mod' Also watch out for triggers modifying stuff. -- Andreas
Joseph Krogh CTO / Partner - Visena AS Mobile: +47 909 56 963 andreas(at)visena(dot)com
<mailto:andreas(at)visena(dot)com> www.visena.com <https://www.visena.com>
<https://www.visena.com>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Achilleas Mantzios 2019-04-09 10:10:34 Re: Transactions
Previous Message Karl Martin Skoldebrand 2019-04-09 09:56:28 RE: Transactions