| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Marti Raudsepp <marti(at)juffo(dot)org>, Torsten Zuehlsdorff <foo(at)meisterderspiele(dot)de>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: How to convert HEX to ASCII? |
| Date: | 2011-12-02 20:54:33 |
| Message-ID: | CAHyXU0znY7dd=+cTevAC=-pOPuqTgp-Cws+v3u2eqGWa9KXrKw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Dec 2, 2011 at 2:01 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>>> so bytea_agg - one param aggregate has sense
>>>
>>> it's very easy to implement it
>>
>> yup:
>>
>> create aggregate bytea_agg (bytea)
>> (
>> sfunc=byteacat,
>> stype=bytea
>> );
>
> this is workaround :)
>
> without a memory preallocating it has same speed like cycle in plpgsql.
sure, but I prefer to code against the workaround because it's cleaner
and it makes things easier to port over when such a feature makes it
into core. also, one liner sql has better chance of inlining as a
general rule.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2011-12-02 21:01:06 | Re: How to convert HEX to ASCII? |
| Previous Message | Jeff Amiel | 2011-12-02 20:52:27 | Re: Oddball data distribution giving me planner headaches |