Re: Bug#98565: postgresql logs notices with GMT timestamps in syslog (fwd)

Started by Oliver Elphickalmost 25 years ago2 messageshackers
Jump to latest
#1Oliver Elphick
olly@lfix.co.uk

Tom Lane wrote:

"Oliver Elphick" <olly@lfix.co.uk> writes:

Notices are being timestamped in GMT in the syslog, instead of local
time like all other log entries. Here's a fragment from my syslog:

Curious. I always assumed that syslog timestamps were supplied by the
syslog daemon, but to make this happen they'd have to be supplied in the
syslog client process (viz. the Postgres process). What timezone is the
Postgres backend being run in, and is it different from all the other
syslog clients on the system?

I just got this extra information from the reporter.

------- Forwarded Message

Date: Thu, 24 May 2001 08:57:49 -0400
From: "Marc Sherman" <msherman@projectile.ca>
To: <98565@bugs.debian.org>
Subject: Bug#98565: More info on this bug

The connection that is creating this NOTICE is executing
"set time zone 'GMT';" immediately after connection; I
suspect that what's happening is that postmaster is setting the
libc timezone (by changing the environment and calling tzset)
when is executes that query, causing subsequent system calls
(including syslog) to use the new timezone.

- - Marc

------- End of Forwarded Message

--
Oliver Elphick Oliver.Elphick@lfix.co.uk
Isle of Wight http://www.lfix.co.uk/oliver
PGP: 1024R/32B8FAA1: 97 EA 1D 47 72 3F 28 47 6B 7E 39 CC 56 E4 C1 47
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C
========================================
"I will praise thee; for I am fearfully and wonderfully
made..." Psalms 139:14

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Oliver Elphick (#1)
Re: Bug#98565: postgresql logs notices with GMT timestamps in syslog (fwd)

"Oliver Elphick" <olly@lfix.co.uk> writes:

I just got this extra information from the reporter.

The connection that is creating this NOTICE is executing
"set time zone 'GMT';" immediately after connection; I
suspect that what's happening is that postmaster is setting the
libc timezone (by changing the environment and calling tzset)
when is executes that query, causing subsequent system calls
(including syslog) to use the new timezone.

Uh-huh. This is not a bug, or at least it's not our bug.

regards, tom lane