Bug #711: Automatic created indexes can in some cases not be referenced to

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