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 <andr...@visena.com> Sent: 09 April 2019 11:41 To: pgsql-general@lists.postgresql.org Subject: Sv: Transactions På tirsdag 09. april 2019 kl. 11:26:29, skrev Karl Martin Skoldebrand <ks0c77...@techmahindra.com<mailto:ks0c77...@techmahindra.com>>: Hi, Is there a way to track “transactions” by default (i.e. without anyone having set up anything specific). The problem I am facing is that users are claiming that settings are disappearing with them doing anything to affect them. It would be good to be able to see what postgresql thinks is going on. *Subscriber adds Severity/BU/Service by ticking the corresponding box in subscriber configuration in WEBAPP. This works for some time. *Subscriber stops receiving selected [tickets]. *Upon checking settings the selected Severity/BU/Service has been unselected. 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 <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. ============================================================================================================================
