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). /M. From: Andreas Joseph Krogh <andreas@xxxxxxxxxx>
På tirsdag 09. april 2019 kl. 11:26:29, skrev Karl Martin Skoldebrand <KS0C77263@xxxxxxxxxxxxxxxx>:
Not "without anyone having set up anything specific", but you can change the setting in postgresql.conf to: log_statement = 'all' and reload the settings. You can now see all SQL executed in the log and can debug what's going on. ============================================================================================================================ Disclaimer: This message
and the information contained herein is proprietary and confidential and
subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html
externally http://tim.techmahindra.com/tim/disclaimer.html
internally within TechMahindra. ============================================================================================================================ |