[HACKERS] Revisiting NAMEDATALEN - Mailing list pgsql-hackers

From Emrul
Subject [HACKERS] Revisiting NAMEDATALEN
Date
Msg-id 1499106661641-5969858.post@n3.nabble.com
Whole thread Raw
Responses Re: [HACKERS] Revisiting NAMEDATALEN
Re: [HACKERS] Revisiting NAMEDATALEN
Re: [HACKERS] Revisiting NAMEDATALEN
List pgsql-hackers
Hi hackers,

This question came up again on Reddit:
https://www.reddit.com/r/PostgreSQL/comments/6kyyev/i_have_hit_the_table_name_length_limit_a_number/
and I thought I'd echo it here.

I totally am on board with short, descriptive names and a good convention. 
However, there are just so many cases where 63 characters can't
descriptively describe a column name.  I've been on projects where we have
one table maybe with only a few thousand records but hundreds of columns
each uniquely describing an attribute on the record.  It is a challenge
bordering on impossible to fit them into a consistently named field of <63
characters that someone can later refer to and know what piece of
information it actually refers to.

Is this something that can be revisited for an upcoming release? Also, are
there any technical problems that would be created by increasing this
attribute?



--
View this message in context: http://www.postgresql-archive.org/Revisiting-NAMEDATALEN-tp5969858.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] Race conditions with WAL sender PID lookups
Next
From: "Joshua D. Drake"
Date:
Subject: Re: [HACKERS] Revisiting NAMEDATALEN