Lists: | pgsql-bugs |
---|
From: | pgsql-bugs(at)postgresql(dot)org |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Bug #711: Automatic created indexes can in some cases not be referenced to |
Date: | 2002-07-12 11:19:58 |
Message-ID: | 20020712111958.DCF8D47589D@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-bugs |
Lasse L. Johnsen (lassejohnsen(at)bulldogcommunications(dot)com) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
Automatic created indexes can in some cases not be referenced to
Long Description
It looks as if automatic created indexes can in some cases not be referenced to because long names are truncated. See example SQL statement below.
Sample Code
# CREATE TABLE WHOIS_BLOCK_TABLE_DATE (
# BLOCK SERIAL UNIQUE,
# CREATE INT, -- Timestamp
# UPDATE INT -- Timestamp
# );
NOTICE: CREATE TABLE will create implicit sequence 'whois_block_table_dat_block_seq' for SERIAL column 'whois_block_table_date.block'
NOTICE: CREATE TABLE / UNIQUE will create implicit index 'whois_block_table_dat_block_key' for table 'whois_block_table_date'
CREATE
# GRANT ALL ON WHOIS_BLOCK_TABLE_DATE_BLOCK_SEQ TO freeipdb;
NOTICE: identifier "whois_block_table_date_block_seq" will be truncated to "whois_block_table_date_block_se"
ERROR: relation "whois_block_table_date_block_se" not found
#
No file was uploaded with this report
From: | Hugo Jonker <hugo(at)gewis(dot)win(dot)tue(dot)nl> |
---|---|
To: | lassejohnsen(at)bulldogcommunications(dot)com, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Bug #711: Automatic created indexes can in some cases not be referenced to |
Date: | 2002-07-12 12:02:57 |
Message-ID: | 20020712140257.Y19515@gewis.win.tue.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-bugs |
On Fri, Jul 12, 2002 at 07:19:58AM -0400, pgsql-bugs(at)postgresql(dot)org wrote:
> Long Description
> It looks as if automatic created indexes can in some cases not be referenced to because long names are truncated. See example SQL statement below.
There's a typo in your statement.
The sequence name gets truncated to 'whois_block_table_dat_block_seq'
instead of 'whois_block_table_date_block_seq',
which is the name you're using in the GRANT statement.
See the two notices:
> NOTICE: CREATE TABLE will create implicit sequence
'whois_block_table_dat_block_seq'
for SERIAL column 'whois_block_table_date.block'
> NOTICE: identifier
"whois_block_table_date_block_seq"
will be truncated to "whois_block_table_date_block_se"
Hugo.
From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | lassejohnsen(at)bulldogcommunications(dot)com, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Bug #711: Automatic created indexes can in some cases not be referenced to |
Date: | 2002-07-12 14:57:24 |
Message-ID: | 9705.1026485844@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-bugs |
pgsql-bugs(at)postgresql(dot)org writes:
> # CREATE TABLE WHOIS_BLOCK_TABLE_DATE (
> # BLOCK SERIAL UNIQUE,
> # CREATE INT, -- Timestamp
> # UPDATE INT -- Timestamp
> # );
> NOTICE: CREATE TABLE will create implicit sequence 'whois_block_table_dat_block_seq' for SERIAL column 'whois_block_table_date.block'
^^^
> NOTICE: CREATE TABLE / UNIQUE will create implicit index 'whois_block_table_dat_block_key' for table 'whois_block_table_date'
> CREATE
> # GRANT ALL ON WHOIS_BLOCK_TABLE_DATE_BLOCK_SEQ TO freeipdb;
^^^^
> NOTICE: identifier "whois_block_table_date_block_seq" will be truncated to "whois_block_table_date_block_se"
> ERROR: relation "whois_block_table_date_block_se" not found
I don't see a bug here. The system told you how it would truncate the name...
regards, tom lane