| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Gasper Zejn <zejn(at)owca(dot)info> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pglz performance |
| Date: | 2019-09-04 09:09:27 |
| Message-ID: | c9af20cf-26e0-092c-910e-700fbd563f44@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-06-24 10:44, Andrey Borodin wrote:
>> 18 мая 2019 г., в 11:44, Andrey Borodin <x4mmm(at)yandex-team(dot)ru> написал(а):
>>
> Hi!
> Here's rebased version of patches.
>
> Best regards, Andrey Borodin.
I think this is the most recent patch for the CF entry
<https://commitfest.postgresql.org/24/2119/>.
What about the two patches? Which one is better?
Have you also considered using memmove() to deal with the overlap issue?
Benchmarks have been posted in this thread. Where is the benchmarking
tool? Should we include that in the source somehow?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2019-09-04 09:22:20 | Re: pglz performance |
| Previous Message | Andres Freund | 2019-09-04 09:08:39 | Re: refactoring - share str2*int64 functions |