On Tue, 2008-02-26 at 14:55 -0500, Tom Lane wrote: > Anyway I think they both have their place.
I think it is very fragile to have the semantics of a builtin datatype change depending on a configure option. It makes it difficult to write applications that depend on the unique properties of *either* of the implementations, and introduces the possibility of subtle portability issues (e.g. your application works fine when developed against a build of Postgres with integer datetimes, but subtly loses precision when used with a floating-point build). It also complicates life for binary-mode clients. If we're convinced that both implementations are worth keeping, IMHO the better route would be to separate them into two distinct sets of datatypes. If not that, then I'd like to see integer datetimes adopted as the default, and FP datetimes deprecated. -Neil ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster