From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andrew Sullivan <andrew(at)libertyrms(dot)info>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: 7.2.3 fixes (was Re: Cause of missing pg_clog files) |
Date: | 2002-09-30 15:30:48 |
Message-ID: | 3D986E28.60404@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> One thing I am undecided about: I am more than half tempted to put in
> the fix that makes us able to cope with mktime's broken-before-1970
> behavior in recent glibc versions (e.g., Red Hat 7.3). This seems like
> a good idea considering that other Linux distros will surely be updating
> glibc soon too. On the other hand, it's hard to call it a critical bug
> fix --- it ain't on a par with the vacuum/clog problem, for sure. And
> the patch has received only limited testing (basically just whatever
> use 7.3beta1 has had). On the third hand, the patch only does something
> if mktime() has already failed, so it's hard to see how it could make
> life worse even if it's buggy.
>
> Any votes on whether to fix that or leave it alone in 7.2.3? I need
> some input in the next few hours ...
>
+1 for fixing it
Joe
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-09-30 15:34:57 | Need Oracle 9 tester. was Re: current_timestamp after queries |
Previous Message | Tom Lane | 2002-09-30 15:29:59 | Re: current_timestamp after queries |