| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Feng Tian <ftian(at)vitessedata(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Decimal64 and Decimal128 |
| Date: | 2017-06-19 19:19:35 |
| Message-ID: | CA+TgmoaU028vpuO+NJgjz_yEs66YkVqY1kzQ9NcHfgwfa5b_mw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 19, 2017 at 1:10 PM, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> On Mon, Jun 19, 2017 at 10:00 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> I've never been very happy with the performance of numeric, so I guess
>> I'm a bit more optimistic about the chances of doing better. Aside
>> from any computational optimizations, the fact that the datatype could
>> be pass-by-value rather than a varlena might speed things up quite a
>> bit in some cases.
>
> What cases do you have in mind?
I don't have a specific use case in mind. However, datumCopy() is
sure to be a lot faster when typByVal is true, and see also the
documentation changes in commit
8472bf7a73487b0535c95e299773b882f7523463.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-06-19 19:27:47 | Re: Preliminary results for proposed new pgindent implementation |
| Previous Message | Satyanarayana Narlapuram | 2017-06-19 19:08:37 | Re: Optional message to user when terminating/cancelling backend |