Re: pg_next_dst_boundary optimization

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
Cc: Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: pg_next_dst_boundary optimization
Date: 2007-09-19 15:03:51
Message-ID: 20473.1190214231@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
> Has anyone looked what other changes there's been to the code in tz
> library?

Yeah, we need to re-sync that code --- one big item we are missing is
support for 64-bit timezone data (hence, tz info beyond 2038). I don't
really want to touch it for 8.3 though. There's been enough code drift
on our side (mostly from well-meaning activities like pg_indent and
ANSI-fying function headers) that a merge is going to be a bit painful,
and risk introducing some bugs. We should hold that for a fresh
devel cycle rather than try to cram it in at the last minute.

> Which version of tz is our code based on?

Whatever was current when we imported the code (4/2004 looks like).

regards, tom lane

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2007-09-19 15:14:20 curious regression failures (was Re: [PATCHES] PL/TCL Patch to prevent postgres from becoming multithreaded)
Previous Message Guillaume Smet 2007-09-19 15:00:24 Re: like/ilike improvements