From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: patch: bytea_agg |
Date: | 2011-12-24 01:44:11 |
Message-ID: | 1324690951-sup-3979@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Excerpts from Pavel Stehule's message of vie dic 23 18:36:11 -0300 2011:
> Hello
>
> 2011/12/23 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> > I generally agree with Peter: string_agg makes sense here. The only
> > real argument against it is Pavel's point that he didn't include a
> > delimiter parameter, but that just begs the question why not. It
> > seems at least plausible that there would be use-cases for it.
>
> I don't know a real usage for bytea delimiter. Probably there is, but
> I expect so most often use case will be without delimiter.
Well, sometimes bytea is used to store character strings when the
encoding information is to be handled by the app instead of having
Postgres know it, for various reasons. I haven't seen any of those
cases yet that would use string_add(bytea) but I wouldn't foreclose that
possibility.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-12-24 02:00:12 | Re: Representation of index clause lists |
Previous Message | Tom Lane | 2011-12-24 00:53:17 | Representation of index clause lists |