Re: change in timestamp output from 8.3 to 8.4 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: change in timestamp output from 8.3 to 8.4
Date
Msg-id 26180.1249258001@sss.pgh.pa.us
Whole thread Raw
In response to change in timestamp output from 8.3 to 8.4  (Joe Conway <mail@joeconway.com>)
Responses Re: change in timestamp output from 8.3 to 8.4  (Joe Conway <mail@joeconway.com>)
Re: change in timestamp output from 8.3 to 8.4  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Joe Conway <mail@joeconway.com> writes:
> 1. Two functions were left in the 8.4 database
>     pg_toasttbl_drop(oid)
>     pg_toasttbl_recreate(oid, oid)

This is pg_migrator's fault --- it should probably clean those up
when it's done.

> 3. All timestamps in the data that have two decimal places on seconds,
>    but end with zero, in the 8.3 dump become one decimal place in the
>    8.4 dump

> I have to apologize for missing it if this has been discussed already,
> but was this change intentional, and if so is there any way to force the
> old behavior?

Yes, it was intentional.  The discussion about changing it was
around here:
http://archives.postgresql.org/pgsql-hackers/2008-10/msg00394.php

There's no exposed way to undo it, but you could probably revert the
logic change in TrimTrailingZeros() until you'd convinced yourself
things were okay.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: machine-readable explain output v4
Next
From: Robert Haas
Date:
Subject: Re: ALTER TABLE ... ALTER COLUMN ... SET DISTINCT