| From: | Ian Lance Taylor <ian(at)airs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Oliver Elphick" <olly(at)lfix(dot)co(dot)uk>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Bug#98565: postgresql logs notices with GMT timestamps in syslog (fwd) |
| Date: | 2001-05-24 18:07:49 |
| Message-ID: | sik8364o3u.fsf@daffy.airs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> "Oliver Elphick" <olly(at)lfix(dot)co(dot)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).
That is correct. The syslog(3) function puts a timestamp in front of
the message, and writes it to the syslog daemon. The string written
to the daemon starts with <N>, where N is the priority and facility
or'ed together.
Ian
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lamar Owen | 2001-05-24 18:09:23 | Re: Not released yet, but could someone take a quick peak ... |
| Previous Message | Mikheev, Vadim | 2001-05-24 18:06:08 | RE: AW: Plans for solving the VACUUM problem |