This Tweet is unavailable.
2
5
Conversation
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
Having a fixed size helps with system catalogs, which have tuples that need to work as regular Postgres heap tuples, but also need to work as pure physical data structures. They can (just for example) sometimes get updated in-place, non-transactionally.
1
3
The existence of a limit is right (and it's documented too). Still, not throwing an error if len(name) > MAXNANELEN is less justifiable...
1
1
2
I was just explaining why the limit exists in the first place, since it's far from obvious. I agree that the truncation issue is nasty. I'm not prepared to say that the limit itself is either right or wrong.
The limit is wrong in the sense that the standard requires a minimum of 128 characters and we only have a maximum of 63 octets.
But that is not what you meant and I know it.
1