Re: Re: patch: fix performance problems with repated decomprimation of varlena values in plpgsql
| От | Noah Misch |
|---|---|
| Тема | Re: Re: patch: fix performance problems with repated decomprimation of varlena values in plpgsql |
| Дата | |
| Msg-id | [email protected] обсуждение исходный текст |
| Ответ на | Re: Re: patch: fix performance problems with repated decomprimation of varlena values in plpgsql (Robert Haas <[email protected]>) |
| Ответы |
Re: Re: patch: fix performance problems with repated
decomprimation of varlena values in plpgsql
Re: Re: patch: fix performance problems with repated decomprimation of varlena values in plpgsql |
| Список | pgsql-hackers |
On Mon, Feb 07, 2011 at 11:16:18PM -0500, Robert Haas wrote: > So > can we just get rid of should_be_detoasted, and have exec_eval_datum() > or its callers instead test: > > !var->isnull && var->datatype->typbyval && var->datatype->typlen == -1 > && VARATT_IS_EXTENDED(var->value) FWIW, this is what I meant by option 2 in my summary. > I haven't tested this, but it's not clear that'd be measurably slower > than checking a single Boolean. Pavel benchmarked this or something close, measuring a performance loss: http://archives.postgresql.org/message-id/[email protected] Tom also expressed concern over performance: http://archives.postgresql.org/message-id/[email protected] Not sure what's next. nm
В списке pgsql-hackers по дате отправления: