Re: [HACKERS] Minor bug: inconsistent handling of overlength names

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane)
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Minor bug: inconsistent handling of overlength names
Date: 1998-08-22 21:15:01
Message-ID: 199808222115.RAA01970@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)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(at)candle(dot)pha(dot)pa(dot)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)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 1998-08-23 08:36:10 Re: [HACKERS] New Developer's FAQ item
Previous Message Oliver Elphick 1998-08-22 16:58:02 Can I distinguish identically named columns in joined tables?