| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Integer datetimes |
| Date: | 2007-05-05 15:38:07 |
| Message-ID: | 1178379487.18303.112.camel@goldbach |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, 2007-05-05 at 11:03 -0400, Tom Lane wrote:
> We've so far managed to avoid having any hard dependency on a working
> int64 type, but this would certainly be one. I don't really think the
> code-size-reduction argument is strong enough to justify that.
What benefit do we get from avoiding this dependency? Can we really
avoid a dependency on a 64-bit integral type in the long run?
> I'm not necessarily opposed to changing the default configure selection,
> but I am opposed to removing the FP code entirely.
I would be satisfied with changing the default to integer and
deprecating the FP code (but keeping it around as a configure option).
Are there any objections to doing this for 8.3?
-Neil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2007-05-05 15:41:18 | Re: Cache plan invalidation |
| Previous Message | Andrew Dunstan | 2007-05-05 15:24:26 | Re: array type name mangling |