From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Tony Griffiths <tony(dot)griffiths(at)cs(dot)man(dot)ac(dot)uk> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Extending table name max length |
Date: | 2002-04-15 17:32:10 |
Message-ID: | 24516.1018891930@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Tony Griffiths <tony(dot)griffiths(at)cs(dot)man(dot)ac(dot)uk> writes:
> I had assumed that there would be a single header file that sets the max
> name length, but it loos like the esql precompiler didn't pick up the
> amended max name length.
Did you remember to recompile ecpg? AFAICT it uses the same NAMEDATALEN
symbol as everyplace else.
In general, when making a system-wide configuration change like that
one, it'd be a good idea to "make clean" at the top level, then do a
full make, make install, initdb cycle.
If you did all that, another possibility is an include file search path
problem: perhaps the ecpg compile picked up a previously-installed
postgres_ext.h with the wrong NAMEDATALEN value.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-04-15 17:40:22 | Re: Databases in memory (-->flashdrive problem) |
Previous Message | Dmitry Tkach | 2002-04-15 17:07:20 | Alter/update large tables - VERRRY annoying behaviour! |