Skip site navigation (1) Skip section navigation (2)

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 (view raw, whole thread or download thread mbox)
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.

	Jeff Davis

In response to


pgsql-hackers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group