Re: [BUGS] Bug in postgres log file - Mailing list pgsql-bugs

From bricklen
Subject Re: [BUGS] Bug in postgres log file
Date
Msg-id CAGrpgQ9PYnVnv=2raVEXVy2KtZVc=_DH7bsGN55ZzdHM1XEZfg@mail.gmail.com
Whole thread Raw
In response to [BUGS] Bug in postgres log file  ("Bogdan Bykhovets - ControlPay" <b.bykhovets@controlpay.com>)
List pgsql-bugs
On Thu, Feb 2, 2017 at 1:14 AM, Bogdan Bykhovets - ControlPay <b.bykhovets@controlpay.com> wrote:
 

Postgres writes in to the log file the same date and time(server starts date and time) for all checkpoint operations. For other operations for example long queries or errors postgres writes in to the log current date and time.

 

> select version();

PostgreSQL 9.6.0 on x86_64-suse-linux-gnu, compiled by gcc (SUSE Linux) 4.3.4 [gcc-4_3-branch revision 152973], 64-bit



Try changing your log_line_prefix to
log_line_prefix = '%p %u %m %e %i'
and reloading your postgresql.conf files (eg. pg_ctl reload)
I suspect the "%s" session timestamp is the problem, and you might be looking for the wall clock time instead (which is logged via "%m")

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: [BUGS] BUG #14525: select .* takes extremely long time
Next
From: jcantin@strategicfuse.com
Date:
Subject: [BUGS] BUG #14527: Calandar Week