Re: [HACKERS] Minor bug: inconsistent handling of overlength names - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Minor bug: inconsistent handling of overlength names
Date
Msg-id 17415.903801570@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Minor bug: inconsistent handling of overlength names  (Bruce Momjian <maillist@candle.pha.pa.us>)
Responses Re: [HACKERS] Minor bug: inconsistent handling of overlength names  (Bruce Momjian <maillist@candle.pha.pa.us>)
Re: [HACKERS] Minor bug: inconsistent handling of overlength names  (Bruce Momjian <maillist@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian <maillist@candle.pha.pa.us> writes:
> I believe Tom Lane has fixed this.
>> On Sun, 26 Jul 1998, Tom Lane wrote:
>>>> DROP INDEX fails on overlength table names:

No, I have *not* fixed it, I only complained about it ;-).

I like your idea of truncating names to 31 characters in the parser;
this should solve the problem globally.  (Most likely, if DROP INDEX
has a bug then the same bug may exist elsewhere as well.)

Is the limit 31 not 32?

            regards, tom lane

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] tuple return from function
Next
From: "Oliver Elphick"
Date:
Subject: Can I distinguish identically named columns in joined tables?