| From: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 14:59:53 |
| Message-ID: | 45F80DE9.2020001@sun.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan wrote:
> Martijn van Oosterhout wrote:
>> I think that from a data integrity point of view the current system is
>> the best. At the very least what you propose is a modularity violation:
>> Postgres depending on undocumented private data of another system
>> component.
>>
>>
>>
>
> I don't think you can reasonably describe the system timezone database
> as undocumented private data. Plenty of other systems rely on it, as we
> used to do.
>
> But I take Tom's point about most users not knowing if their TZ database
> is usable or not. Maybe we need a tool (maybe on pgfoundry) that will do
> some analysis to find out, if such a thing is possible.
I guess some regression test should test TZ validity?
Zdenek
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-03-14 15:05:39 | Re: Daylight Saving Time question PostgreSQL 8.1.4 |
| Previous Message | Hannu Krosing | 2007-03-14 14:59:39 | Re: [PATCHES] Bitmapscan changes |