Re: [HACKERS] more on int8

From: "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: daniel(at)digsys(dot)bg, pgsql-hackers(at)hub(dot)org
Subject: Re: [HACKERS] more on int8
Date: 1998-09-11 15:53:13
Message-ID: 35F94769.4FF18691@alumni.caltech.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> We could probably do without %qd, but I assume their are some
> platforms that support %qd and not %lld. We can ask people as they
> run configure if they ever see %lld failing but %qd passing.

Could we please leave all of the hooks for %qd in the code, but disable
the automatic check for it in configure.in and configure? If we run into
a case which requires it, then it will be trivial to re-enable it (or if
you like allow a manual override --enable-int8-qd). If we do not run
into such a case then we can remove the code later, simplifying things a
bit.

If we don't disable it for now, then we will never be able to discover
whether it is a required feature or not. Now is the time to do this
since int8 is a new feature. It won't work very well to try the same
tactic 6 months from now :)

Thanks.

- Tom

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas G. Lockhart 1998-09-11 16:17:12 Re: [HACKERS] pg_user problem
Previous Message Joost Kraaijeveld 1998-09-11 15:51:23 RE: [HACKERS] Missing headers Windows NT port