| From: | Ben Chobot <bench(at)silentmedia(dot)com> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Inconsistent time interval formatting |
| Date: | 2011-01-13 23:38:53 |
| Message-ID: | D448F91F-8F36-4FA2-8495-0A592E33FA99@silentmedia.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Jan 13, 2011, at 1:15 PM, John R Pierce wrote:
> On 01/13/11 1:08 PM, Ben Chobot wrote:
>> On Jan 13, 2011, at 11:03 AM, Tom Lane wrote:
>>
>>> If you don't care about that, you can use justify_hours (I think that's
>>> the right function) to smash them to the same thing.
>> I use justify_hours, and I still get entries like '1 day 35:31:10' intermixed with the entires I'd expect like '2 days 03:12:40'.
Ho ho... for the record, it turns out that the one column in our report which has these issues is the one somebody forgot got wrap with justify_hours.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dan Birken | 2011-01-13 23:55:11 | Re: Question about concurrent synchronous and asynchronous commits |
| Previous Message | Adrian Klaver | 2011-01-13 22:45:35 | Re: Inconsistent time interval formatting |