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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Minor bug: inconsistent handling of overlength names
Date: 1998-08-22 15:59:30
Message-ID: 17415.903801570@sss.pgh.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?

regards, tom lane

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Meskes 1998-08-22 16:09:34 Re: [HACKERS] initdb problem
Previous Message Bruce Momjian 1998-08-22 12:40:21 Re: [HACKERS] tuple return from function