| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
| Cc: | Jeremy Drake <pgsql(at)jdrake(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: width_bucket function for timestamps |
| Date: | 2006-10-09 16:02:12 |
| Message-ID: | 2608.1160409732@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Jim C. Nasby" <jim(at)nasby(dot)net> writes:
> Sinte we already have width_bucket, I'd argue this should go in core. If
> someone's feeling adventurous, there should probably be a double
> precision version as well. Hrm... and maybe text...
It's not clear to me why we have width_bucket operating on numeric and
not float8 --- that seems like an oversight, if not outright
misunderstanding of the type hierarchy. But if we had the float8
version, I think Jeremy's problem would be solved just by applying
the float8 version to "extract(epoch from timestamp)". I don't really
see the use-case for putting N versions of the function in there.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2006-10-09 16:07:30 | Re: Upgrading a database dump/restore |
| Previous Message | Jim C. Nasby | 2006-10-09 15:53:47 | Re: width_bucket function for timestamps |