From: | Alvaro Herrera <alvherre(at)surnet(dot)cl> |
---|---|
To: | Darren Houston <darren(dot)houston(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Problem - PostgreSQL Truncating Column Names to 63 Characters |
Date: | 2005-05-13 16:57:34 |
Message-ID: | 20050513165734.GB15325@surnet.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, May 13, 2005 at 10:07:43AM -0600, Darren Houston wrote:
> Hello everyone,
>
> I guess I'm not typing in the right search string for my question
> because I can't find any answer on the Internet. So I'm coming to all
> of you for help.
>
> I'm performing a cross-tab type query in PostgreSQL where the returned
> data in rows become my column names. The problem I'm facing is that
> PostgreSQL is truncating the column names down to 63 characters, and
> some of my names need to be a little larger than that. Is a 63 column
> name length a limit in PostgreSQL, or is there a
> setting/function/compile time option I can enact to overcome this
> problem?
Yes, you can change it at compile time. It's the NAMEDATALEN
definition. Don't expect the resulting data directory to be compatible
with vanilla sources though -- you will only be able to use that with
patches sources. Of course, if you produce dump files with long names,
they will be truncated if exported into nonpatched systems too, so take
caution.
--
Alvaro Herrera (<alvherre[a]surnet.cl>)
"La primera ley de las demostraciones en vivo es: no trate de usar el sistema.
Escriba un guión que no toque nada para no causar daños." (Jakob Nielsen)
From | Date | Subject | |
---|---|---|---|
Next Message | Darren Houston | 2005-05-13 17:33:18 | Re: Problem - PostgreSQL Truncating Column Names to 63 Characters |
Previous Message | Tom Lane | 2005-05-13 16:55:48 | Re: Problem - PostgreSQL Truncating Column Names to 63 Characters |