Re: Floating-point timestamps versus Range Types - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: Floating-point timestamps versus Range Types
Date
Msg-id 1288032709.9047.5.camel@jdavis-ux.asterdata.local
Whole thread Raw
In response to Re: Floating-point timestamps versus Range Types  (James Cloos <cloos@jhcloos.com>)
Responses Re: Floating-point timestamps versus Range Types
List pgsql-hackers
On Mon, 2010-10-25 at 13:54 -0400, James Cloos wrote:
> >>>>> "JD" == Jeff Davis <pgsql@j-davis.com> writes:
> 
> JD> 2. Fix the input/output functions in a special mode for dump/reload,
> JD>    to make them true inverses.
> 
> That can be done by supporting the %A printf(3)/scanf(3) format.

I don't happen to see a %A format in the man page, but I doubt the
output would look like a timestamp. And if it doesn't look like a
timestamp, it violates the spirit of a logical dump of the data.

We could just base64-encode the binary and print that, but that doesn't
maintain the spirit of a logical data dump either.

Regards,Jeff Davis



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: add label to enum syntax
Next
From: Peter Eisentraut
Date:
Subject: foreign keys for array/period contains relationships