On 07/27/2015 12:36 PM, JotaComm wrote:
>
> Hello,
>
> I have the following inconsistency in my environment:
>
> postgres@postgres =# SELECT current_timestamp;
> now
> -------------------------------
> *2015-07-27 16:26:40.001694-03*
> (1 row)
>
> postgres@postgres =# SHOW timezone;
> TimeZone
> -------------
> Brazil/East
> (1 row)
>
> postgres@postgres =# SELECT blah;
> ERROR: column "blah" does not exist
>
> In my log file:
>
> [*2015-07-27 19:27:10.944 GMT*] 3397 <postgres postgres [local] 42703>
> ERROR: column "blah" does not exist at character 8
> [*2015-07-27 19:27:10.944 GMT*] 3397 <postgres postgres [local] 42703>
> STATEMENT: SELECT blah;
>
> My PostgreSQL version is: 9.2.4
>
> cat /etc/issue
> CentOS release 6.3 (Final)
> Kernel \r on an \m
>
> Could you help me?
http://www.postgresql.org/docs/9.2/interactive/runtime-config-logging.html
log_timezone (string)
Sets the time zone used for timestamps written in the server log.
Unlike TimeZone, this value is cluster-wide, so that all sessions will
report timestamps consistently. The built-in default is GMT, but that is
typically overridden in postgresql.conf; initdb will install a setting
there corresponding to its system environment. See Section 8.5.3 for
more information. This parameter can only be set in the postgresql.conf
file or on the server command line.
>
> Thanks a lot.
>
> Best regards
>
>
> --
> JotaComm
> http://jotacomm.wordpress.com
--
Adrian Klaver
adrian.klaver@aklaver.com