Skip site navigation (1) Skip section navigation (2)

Re: Bug 1500

From: Steve Crawford <scrawford(at)pinpointresearch(dot)com>
To: Lyubomir Petrov <lpetrov(at)sysmaster(dot)com>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: Bug 1500
Date: 2005-03-25 20:53:53
Message-ID: 200503251253.54061.scrawford@pinpointresearch.com (view raw or flat)
Thread:
Lists: pgsql-hackers
> So this bug actually brings the issue of interval to_char()
> formatting. Opinions?

In digging around I discovered that it appears a decision was made to 
remove to_char(interval) at the 8.1 release but I've been unable to 
find the replacement for this functionality. This alarms me.

Given the messages I've seen regarding to_char(interval), it's clearly 
a function that is used. As an example, in our telephony systems 
there is a column for start_time and for end_time. Billing involves a 
sum(end_time-start_time) for the appropriate project/client/period. 
Naturally, that interval needs to be displayed appropriately.

The most common request I've seen (and it would be very helpful for me 
as well) is the ability to fill the largest displayed time increment 
with all remaining time in the interval.

In other words when the total increment is 7 days, 7 hours, 28 
minutes, 12 seconds the desired output would be 10528 minutes 12 
seconds. Think phone-billing, race times, mission clocks, etc.

So...

1) Is there really a plan to eliminate to_char(interval)?

2) If so, what is the replacement?

3) If there isn't a replacement and it's just scheduled for 
elimination, what harm was to_char(interval) causing to require its 
removal and what's the best way to lobby for its retention and 
improvement?

Cheers,
Steve


In response to

  • Bug 1500 at 2005-03-25 19:54:40 from Lyubomir Petrov

Responses

pgsql-hackers by date

Next:From: Matthew T. O'ConnorDate: 2005-03-25 21:04:25
Subject: Re: pg_autovacuum not having enough suction ?
Previous:From: Otto BlomqvistDate: 2005-03-25 20:35:00
Subject: Re: pg_autovacuum not having enough suction ?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group