Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: [HACKERS] win32 crash in initdb
- From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
- To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
- Cc: <pgsql-hackers-win32(at)postgresql(dot)org>, "PostgreSQL-patches" <pgsql-patches(at)postgresql(dot)org>
- Subject: Re: [HACKERS] win32 crash in initdb
- Date: Thu, 29 Jul 2004 19:10:06 +0200
- Message-id: <6BCB9D8A16AC4241919521715F4D8BCE34BF77(at)algol(dot)sollentuna(dot)se>
>> The crash people are getting in initdb is due to the 1.19 revision to >> pgtz.c. Not sure why yet...looking into it... > >Unfortunate behavior when probing pre-1970 dates, maybe? Indeed that was the problem. Attached patch fixes the issue here and for Merlin :-) I've also figured out why it always worked for me. When in the western europe timezone, the bug does not show up (probably because we don't probe those dates). When I set my system to US Eastern, it broke. //Magnus
Attachment:
tzfix.patch
Description: tzfix.patch
- Follow-Ups:
- Re: [HACKERS] win32 crash in initdb
- From: Tom Lane
- Re: [HACKERS] win32 crash in initdb
- Prev by Date: Re: localtime() for win32 problem.
- Next by Date: Re: [HACKERS] win32 crash in initdb
- Previous by thread: win32 crash in initdb
- Next by thread: Re: [HACKERS] win32 crash in initdb
- Indexes: