Re: Unable to log in current local time EST - Mailing list pgsql-general

From Alex Lai
Subject Re: Unable to log in current local time EST
Date
Msg-id f23c5072-f963-5cf7-bb54-46bf965b12b0@sesda3.com
Whole thread Raw
In response to Unable to log in current local time EST  (Alex Lai <mlai@sesda3.com>)
List pgsql-general
On 08/25/2016 11:36 AM, Alex Lai wrote:
> Dear All,
>
> I have my log_line_prefix set to
> log_line_prefix = '[%d]%p %x %c[%l] %t %i'
> in postgresql.conf
>
> psql -c 'show timezone'
>   TimeZone
> ------------
>  US/Eastern
>
> tail -2 omi_acps.log ; date
> [sipsdb]20180 0 57ab7dcd.4ed4[11895717] 2016-08-25 15:32:45 GMT
> SELECTLOG:  duration: 0.326 ms
> [sipsdb]20180 0 57ab7dcd.4ed4[11895718] 2016-08-25 15:32:45 GMT idle in
> transactionLOG:  statement: fetch all in "<unnamed portal 854341>"
> Thu Aug 25 11:32:45 EDT 2016
> My host is running EST time.
>
> Postgres keeps log the GMT time.
> I want to log EST time.  How can I do that?  Your help would be greatly
> appreciated.
>
>
>
Actually, I found the problem.  I missed the parameter log_timezone.  It
took by default as GMT.  I added log_timezone=US/Eastern and run
pg_ctl reload.

It works.

--
Best regards,

Alex Lai  (:-)
OMP SIPS DBA ADNET Systems, Inc.

7515 Mission Drive, Suite A100
Lanham, MD 20706
301 352-4657 (phone)
301 352-0437 (fax)
mlai@sesda3.com


pgsql-general by date:

Previous
From: Devrim Gündüz
Date:
Subject: Re: Unable to log in current local time EST
Next
From: Ahsan Ali
Date:
Subject: Re: LOG: could not fork new process for connection: Cannot allocate memory