| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stéphane Schildknecht <stephane(dot)schildknecht(at)postgresqlfr(dot)org> |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Timestamp precision |
| Date: | 2007-03-29 15:14:57 |
| Message-ID: | 22125.1175181297@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
=?ISO-8859-1?Q?St=E9phane_Schildknecht?= <stephane(dot)schildknecht(at)postgresqlfr(dot)org> writes:
> In fact, I wonder why a date ranging from somme 4000 BC to 30000 AC is
> stored as a reference to the 1st january of 2000. Is it because that day
> is some "close to actual time" date ?
The restriction to 4713BC comes from the Julian-date calendar
manipulation algorithms, not from the possible range of the underlying
integer or float.
> And so, what do you mean by "within a few years"?
It means we didn't bother to write out the math. If you know the
precision of float8 on your hardware (2^-53 for IEEE) you can work
it out for yourself...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-03-29 15:17:25 | Re: COPY command details |
| Previous Message | Jasbinder Singh Bali | 2007-03-29 15:11:47 | Re: cursors in postgres |