From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | jim(at)reptiles(dot)org (Jim Mercer) |
Cc: | reedstrm(at)wallace(dot)ece(dot)rice(dot)edu (Ross J(dot) Reedstrom), pgsql-general(at)postgreSQL(dot)org, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] getting at the actual int4 value of an abstime |
Date: | 1999-08-18 14:26:39 |
Message-ID: | 24793.934986399@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
jim(at)reptiles(dot)org (Jim Mercer) writes:
> [ concern about speed of converting datetime values to/from text for
> Postgres ]
FWIW, I used to be really concerned about that too, because my
applications do lots of storage and retrieval of datetimes.
Then one day I did some profiling, and found that the datetime
conversion code was down in the noise. Now I don't worry so much.
It *would* be nice though if there were some reasonably cheap documented
conversions between datetime and a standard Unix time_t displayed as a
number. Not so much because of speed, as because there are all kinds
of ways to get the conversion wrong on the client side --- messing up
the timezone and not coping with all the Postgres datestyles are two
easy ways to muff it.
BTW, I believe Thomas is threatening to replace all the datetime-like
types with what is currently called datetime (ie, a float8 measuring
seconds with epoch 1/1/2000), so relying on the internal representation
of abstime would be a bad idea...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 1999-08-18 14:42:58 | Re: [GENERAL] CVS Import/Export |
Previous Message | Bruce Tong | 1999-08-18 14:14:49 | CVS Import/Export |
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 1999-08-18 14:42:58 | Re: [GENERAL] CVS Import/Export |
Previous Message | Bruce Tong | 1999-08-18 14:14:49 | CVS Import/Export |