| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Alvaro Herrera <alvherre(at)CommandPrompt(dot)com>, Devrim GÜNDÜZ <devrim(at)CommandPrompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: New tzdata available |
| Date: | 2007-11-09 16:09:19 |
| Message-ID: | 10951.1194624559@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> writes:
> Another interesting questions are what postgres does when timezone files
> are changed? Does it need SIGHUP to invoke rereading? What is impact on
> current running transaction when tz file is changed?
This falls into the category of "get a life". There is no program in
the world that automatically reacts to timezone data updates. The
normal expectation is that you reboot, because such always-on daemons as
"cron" will already have read the timezone file into memory. The libc
API doesn't even provide a way that one could tell libc to re-read after
SIGHUP, say.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-11-09 16:33:45 | Re: [HACKERS] Estimation problem with a LIKE clause containing a / |
| Previous Message | Greg Smith | 2007-11-09 14:56:08 | Re: Feature request concerning postmaster log file. |