Re: Floating-point timestamps versus Range Types

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: James Cloos <cloos(at)jhcloos(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Floating-point timestamps versus Range Types
Date: 2010-10-25 18:51:49
Message-ID: 1288032709.9047.5.camel@jdavis-ux.asterdata.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 2010-10-25 at 13:54 -0400, James Cloos wrote:
> >>>>> "JD" == Jeff Davis <pgsql(at)j-davis(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Divakar Singh 2010-10-25 18:52:31 Re: Postgres insert performance and storage requirement compared to Oracle
Previous Message Robert Haas 2010-10-25 18:51:42 Re: add label to enum syntax