Well, I know the source of your problems, if not the solution...
(from the docs) time, timestamp, and interval accept an optional precision
value p which specifies the number of fractional digits retained in the
seconds field. By default, there is no explicit bound on precision. The
effective limit of precision is determined by the underlying double
precision floating-point number used to store values (in seconds for
interval and in seconds since 2000-01-01 for timestamp). The useful range of
p is from 0 to about 6 for timestamp, but may be more for interval. The
system will accept p ranging from 0 to 13.
http://www7.us.postgresql.org/users-lounge/docs/7.2/postgres/datatype-dateti
me.html
I didn't see anything specific about reverting back to the old format, but
this might help point you in the right direction
Robert
> -----Original Message-----
> From: pgsql-general-owner@postgresql.org
> [mailto:pgsql-general-owner@postgresql.org]On Behalf Of Matteo Beccati
> Sent: Monday, February 25, 2002 12:43 PM
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] Timestamp output
>
>
> Hi,
>
> I've just upgraded to 7.2, and found a big difference in timestamp
> output. I'm using the default ISO datestyle, and newly inserted
> timestamp output looks like that:
>
> 2002-02-25 16:50:49.289828+01
>
> What is the ".289828" which is breaking all my php scripts?
>
> Can I easily revert to the previous format?
>
> Thank you
> --
> Matteo Beccati
> C.R.P. Software S.r.l.
> http://www.crpsoftware.it/
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>
