From: | Michael Meskes <meskes(at)postgresql(dot)org> |
---|---|
To: | Kris Jurka <books(at)ejurka(dot)com> |
Cc: | PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: NetBSD/dtime_t |
Date: | 2008-02-16 09:00:48 |
Message-ID: | 20080216090048.GA6702@feivel.credativ.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Feb 15, 2008 at 05:07:17PM -0500, Kris Jurka wrote:
>> Could anyone please tell me how NetBSD defines dtime_t? We have a
>> buildfarm failure on canary.
>
> /usr/include/sys/types.h says:
>
> typedef int32_t dtime_t; /* on-disk time_t */
Thanks. I wonder why they define this datatype. I didn't find it on any
other architecture.
Anyway, does anyone have a suggestion how to solve this issue? Informix
uses the dtime_t datatype to store a timestamp. pgtypeslib also defines
a timestamp type which is 64 bit and not 32 bit like the NetBSD one.
Informix compatibility now typedefs dtime_t to timestamp so the
functions with Informix syntax work as advertized.
If I do not define this datatype, Informix compatibility will not work,
if I define it, NetBSD is not able to compile to regression tests. Of
course we can work around the regression test problem, but a user using
the Informix compatibility feature on NetBSD will run into the same
problem.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes(at)jabber(dot)org
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-02-16 14:15:24 | Re: NetBSD/dtime_t |
Previous Message | Tom Lane | 2008-02-16 02:35:24 | PG-relevant bug fixes just pushed in Fedora 8 |