| 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 17:49:37 |
| Message-ID: | 4187.1160416177@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:
> On Mon, Oct 09, 2006 at 12:02:12PM -0400, Tom Lane wrote:
>> ... I think Jeremy's problem would be solved just by applying
>> the float8 version to "extract(epoch from timestamp)".
Thinko there ... I meant to type "extract(epoch from interval)".
> Well, it would be nice to have a timestamp version so that users didn't
> have to keep typing "extract(epoch from timestamp)"... but yeah, I
> suspect that would work fine for timestamps. For intervals I suspect you
> could just convert to seconds (if we're going to add timestamps, it
> seems like we should add intervals as well).
This is exactly the slippery slope I don't care to start down.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Browne | 2006-10-09 17:56:41 | Re: OT: Is there a LinkedIn group for Postgresql? |
| Previous Message | Jim C. Nasby | 2006-10-09 17:38:55 | Re: width_bucket function for timestamps |