Re: Re: patch: fix performance problems with repated decomprimation of varlena values in plpgsql - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: patch: fix performance problems with repated decomprimation of varlena values in plpgsql
Date
Msg-id 19610.1295967798@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: patch: fix performance problems with repated decomprimation of varlena values in plpgsql  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Re: patch: fix performance problems with repated decomprimation of varlena values in plpgsql  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> Detoasting on first usage, ie. exec_eval_datum(), seems the best to me. 
> Compared to detoasting on assignment, it avoids the performance 
> regression if the value is never used, and I don't think checking if the 
> value is toasted at every exec_eval_datum() call adds too much overhead.

The arguments that were made against this were about maintenance costs
and code footprint.  Claims about performance are not really relevant,
especially when they're entirely unsupported by evidence.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Is there a way to build PostgreSQL client libraries with MinGW
Next
From: Dimitri Fontaine
Date:
Subject: Re: Extensions support for pg_dump, patch v27