Thank Adrian for response.
Yes I have the same *.conf file as v11.5 in fact I have copied the same conf files in v12.2 Logging parameter are as follows Parameter Values log_autovacuum_min_duration 1s log_checkpoints on log_connections on log_destination stderr log_directory log log_disconnections on log_duration off log_error_verbosity default log_executor_stats off log_file_mode 600 log_filename postgresql-%Y-%m-%d_%H%M%S.log log_hostname off log_line_prefix %m %d %u %l %s pid:%p xid:%x ip:%h log_lock_waits on log_min_duration_statement -1 log_min_error_statement error log_min_messages warning log_parser_stats off log_planner_stats off log_replication_commands on log_rotation_age 1h log_rotation_size 0 log_statement none log_statement_stats off log_temp_files 0 log_transaction_sample_rate 0 log_truncate_on_rotation on logging_collector on Thanks & Regards, Ishan Joshi -----Original Message----- From: Adrian Klaver <adrian.kla...@aklaver.com> Sent: Tuesday, May 19, 2020 7:28 PM To: Ishan Joshi <ishan.jo...@amdocs.com>; pgsql-gene...@postgresql.org Subject: Re: idle_in_transaction_session_timeout not getting log in PG v12.2 On 5/19/20 2:08 AM, Ishan Joshi wrote: > Hi Team, > > I have set idle_in_transaction_session_timeout on user level and it is > set for 5 min. I can see after 5 min the session with "idle in > transaction" state got killed and it log the details in postgresql log > file with "FATAL: terminating connection due to idle-in-transaction > timeout" in v11.5 > > But I have testing the same in v12.2, The session getting killed with > state "idle in transaction" but the log is not generated in > postgresql log file. > > Is there any specific changes related to this for v12.2 or any > additional parameters need to set for generating logs. Looking at code in ~/backend/tcop/postgres.c it has not changed. Are you reusing the same *.conf in 12 as you did in 11? What are your logging settings? > > Thanks & Regards, > > Ishan Joshi > > *This email and the information contained herein is proprietary and > confidential and subject to the Amdocs Email Terms of Service, which > you may review > at**https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.amdocs.com%2Fabout%2Femail-terms-of-service*&data=02%7C01%7CIs<http://www.amdocs.com%2Fabout%2Femail-terms-of-service*&data=02%7C01%7CIs> > han.Joshi%40amdocs.com%7C7d8dce6a7c7d4349a7ec08d7fbfcccd5%7Cc8eca3ca12 > 7646d59d9da0f2a028920f%7C0%7C0%7C637254935514522274&sdata=Gi7j8rno > ogMRCpaAWM0UuH%2FzorFKy9vnpeEfNfu1dLo%3D&reserved=0 > -- Adrian Klaver adrian.kla...@aklaver.com<mailto:adrian.kla...@aklaver.com> This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service <https://www.amdocs.com/about/email-terms-of-service>
