2011/12/2 Merlin Moncure <mmoncure@xxxxxxxxx>: > On Fri, Dec 2, 2011 at 11:15 AM, Pavel Stehule <pavel.stehule@xxxxxxxxx> wrote: >> 2011/12/2 Merlin Moncure <mmoncure@xxxxxxxxx>: >>> On Fri, Dec 2, 2011 at 10:42 AM, Marti Raudsepp <marti@xxxxxxxxx> wrote: >>>> Sorry, but AFAICT this makes a mess of encodings and only works by >>>> pure luck. The server thinks it's sending the client LATIN1 text, but >>>> it's actually UTF8-encoded and the last decoding step is done by your >>>> terminal. >>> >>> yup -- your're right -- what a coincidence! I still prefer the 1 >>> liner sql variant vs plpgsql loop though. nicely done. >> >> 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. Regards Pavel > > merlin -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
