| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Peter Geoghegan <peter(at)2ndquadrant(dot)com>, Ants Aasma <ants(at)cybertec(dot)at>, Greg Smith <greg(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Patch: add timing of buffer I/O requests |
| Date: | 2012-04-25 21:37:44 |
| Message-ID: | CA+TgmobHFd0_RP0vu3g6SMc1K_=ct+DNifQcV9J3wRYSSarZRA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 25, 2012 at 5:33 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>> On mån, 2012-04-23 at 22:03 -0400, Robert Haas wrote:
>>> Perhaps, but nobody's explained what we gain out of NOT using numeric.
>
>> So if you want to have possibly different internal and external
>> representations, why not use interval for the external one?
>
> That doesn't add any usefulness, only extra complication for clients
> that want to do more arithmetic with the values. Also, as was pointed
> out earlier, we have a hard-coded restriction to microsecond precision
> with the default implementation of interval; and it's not hard to
> foresee the day when that won't do.
Agreed.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2012-04-25 22:46:33 | Re: Temporary tables under hot standby |
| Previous Message | Tom Lane | 2012-04-25 21:33:08 | Re: Patch: add timing of buffer I/O requests |