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

From Bruce Momjian
Subject Re: [HACKERS] Minor bug: inconsistent handling of overlength names
Date
Msg-id 199808222115.RAA01970@candle.pha.pa.us
Whole thread Raw
In response to Re: [HACKERS] Minor bug: inconsistent handling of overlength names  (Tom Lane <tgl@sss.pgh.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?

31.  Used to be 32 around 6.0, but all the code to compare non-null
terminated strings in the backend just wasn't worth it.

--
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
  +  If your life is a hard drive,     |  (610) 353-9879(w)
  +  Christ can be your backup.        |  (610) 853-3000(h)

pgsql-hackers by date:

Previous
From: "Oliver Elphick"
Date:
Subject: Can I distinguish identically named columns in joined tables?
Next
From: jwieck@debis.com (Jan Wieck)
Date:
Subject: Re: [HACKERS] New Developer's FAQ item