| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Noah Misch <noah(at)leadboat(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: patch: fix performance problems with repated decomprimation of varlena values in plpgsql |
| Date: | 2011-01-19 17:01:09 |
| Message-ID: | AANLkTim+J-bsxOW_1kjVRVWH-u0jUtfxwzhDVTHx_05j@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2011/1/19 Robert Haas <robertmhaas(at)gmail(dot)com>:
> On Tue, Jan 18, 2011 at 5:22 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>> opinion isn't strong in this topic. One or twenty useless detoasting
>> isn't really significant in almost use cases (problem is thousands
>> detoasting).
>
> Yeah. Many-times-repeated detoasting is really bad, and this is not
> the only place in the backend where we have this problem. :-(
>
???
some general solution can be pretty hardcore - some like handlers
instead pointers on varlena :(
I know mainly about plpgsql performance problems - but it is my
interes. Plpgsql can be simply fixed - maybe 10 maybe less lines of
code.
Pavel
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-01-19 17:05:39 | Re: Replication logging |
| Previous Message | Bruce Momjian | 2011-01-19 16:59:14 | Re: Replication logging |