Re: Patch to improve a few appendStringInfo* calls - Mailing list pgsql-hackers

From David Rowley
Subject Re: Patch to improve a few appendStringInfo* calls
Date
Msg-id CAKJS1f8acVwM-dsPn1rfOj+pmwLLXOBsPoUKteO4iURzuzfCTg@mail.gmail.com
Whole thread Raw
In response to Re: Patch to improve a few appendStringInfo* calls  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Patch to improve a few appendStringInfo* calls  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 22 December 2015 at 01:58, Robert Haas <robertmhaas@gmail.com> wrote:
On Thu, Jul 2, 2015 at 6:08 AM, David Rowley
<david.rowley@2ndquadrant.com> wrote:
>> I left out the changes like
>>
>>> -               appendStringInfoString(&collist, buf.data);
>>> +               appendBinaryStringInfo(&collist, buf.data, buf.len);
>>
>>
>> because they're not an improvement in readablity, IMHO, and they were not
>> in performance-critical paths.
>
> Perhaps we can come up with appendStringInfoStringInfo at some later date.

concatenateStringInfo?


 According to grep -rE "appendStringInfoString\(.*\.data\);" . we have 13 such matches. None of them seem to be in very performance critical places, perhaps with the exception of xmlconcat().

Would you say that we should build a macro to wrap up a call to appendBinaryStringInfo() or invent another function which looks similar?


--
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: plpgsql - DECLARE - cannot to use %TYPE or %ROWTYPE for composite types
Next
From: Haribabu Kommi
Date:
Subject: Re: Parallel Aggregate