| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>, josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org, mledford(at)ugaalum(dot)uga(dot)edu |
| Subject: | Re: Daylight Saving Time question PostgreSQL 8.1.4 |
| Date: | 2007-03-14 15:21:17 |
| Message-ID: | 22781.1173885677@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> What is the actual problem being solved here? That people expected the
> timezone changes to be picked up automatically? think if you weigh it
> up, that problem is less significant than: ...
One other point is that symlinking to system timezone info will not
cause Postgres to "pick up changes automatically". You'll probably
still need a postmaster restart to get the new settings loaded in.
If the timezone info update is delivered as part of a Postgres update,
the need for this is fairly obvious, but if it's happening as part
of an update of a seemingly unrelated package, not so much.
To me, the idea of linking to system timezone info is a convenience
for packagers, and it is (and should be) the packagers' responsibility
to determine whether it's a sane idea for their environment. If they
are competent to determine that, they are certainly competent enough
to make it happen without assistance from our configure script.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2007-03-14 15:21:53 | Re: [PATCHES] Bitmapscan changes |
| Previous Message | mark | 2007-03-14 15:08:23 | Re: My honours project - databases using dynamically attached entity-properties |