Truncation of object names

From: ncm(at)zembu(dot)com (Nathan Myers)
To: pgsql-hackers(at)postgresql(dot)org
Subject: Truncation of object names
Date: 2001-04-13 17:50:31
Message-ID: 20010413105031.A16922@store.zembu.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 13, 2001 at 01:16:43AM -0400, Tom Lane wrote:
> ncm(at)zembu(dot)com (Nathan Myers) writes:
> > We have noticed here also that object (e.g. table) names get truncated
> > in some places and not others. If you create a table with a long name,
> > PG truncates the name and creates a table with the shorter name; but
> > if you refer to the table by the same long name, PG reports an error.
>
> Example please? This is clearly a bug.

Sorry, false alarm. When I got the test case, it turned out to
be the more familiar problem:

create table foo_..._bar1 (id1 ...);
[notice, "foo_..._bar1" truncated to "foo_..._bar"]
create table foo_..._bar (id2 ...);
[error, foo_..._bar already exists]
create index foo_..._bar_ix on foo_..._bar(id2);
[notice, "foo_..._bar_ix" truncated to "foo_..._bar"]
[error, foo_..._bar already exists]
[error, attribute "id2" not found]

It would be more helpful for the first "create" to fail so we don't
end up cluttered with objects that shouldn't exist, and which interfere
with operations on objects which should.

But I'm not proposing that for 7.1.

Nathan Myers
ncm(at)zembu(dot)com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-04-13 18:01:06 Re: timeout on lock feature
Previous Message Tom Lane 2001-04-13 17:25:39 Re: Re: HOLD THE PRESSES!! ... pg_dump from v7.0.3 can't import to v7.1?