From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Ross J(dot) Reedstrom" <reedstrm(at)wallace(dot)ece(dot)rice(dot)edu> |
Cc: | Finn Kettner <fk(at)akf(dot)dk>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Long table names |
Date: | 1999-08-16 21:16:30 |
Message-ID: | 2875.934838190@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Ross J. Reedstrom" <reedstrm(at)wallace(dot)ece(dot)rice(dot)edu> writes:
> As you can see, the table name has been truncated to make the whole
> thing fit into 32 characters. You'd need to check the source to see the
> exact algorithm: I'm not sure if it starts trimming on the field name,
> ever.
Right now, the algorithm is to preferentially truncate the longer name
component (table name or column name). There was some talk of adding
quasi-random hash characters to reduce the probability of name
collisions, but it's not been done.
Anyway, to answer the question Finn asked,
>> I remember someone talking about compiling pgsql so that it could use
>> table names longer than 32 bytes, but that it would require some
>> changes in the source code. Could anyone tell me what changes these
>> are,
In theory you should only have to change NAMEDATALEN, rebuild, and
initdb. I think someone reported a few months on actually trying
this experiment (probably, around the same time we decided to put in
the name-truncation logic); check the pghackers archives for details.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 1999-08-16 21:42:27 | Re: [HACKERS] Re: your mail |
Previous Message | Bruce Momjian | 1999-08-16 20:33:28 | Re: [HACKERS] README.locale patch 2 |