Re: change in timestamp output from 8.3 to 8.4

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>
Subject: Re: change in timestamp output from 8.3 to 8.4
Date: 2009-08-03 00:06:41
Message-ID: 26180.1249258001@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joe Conway <mail(at)joeconway(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-08-03 00:31:48 Re: ALTER TABLE ... ALTER COLUMN ... SET DISTINCT
Previous Message Tom Lane 2009-08-02 23:57:48 Re: machine-readable explain output v4