Alvaro Herrera <alvhe...@2ndquadrant.com> writes:
> I also admit it didn't occur to me to test the function(s) against
> overlength input when developing it. I wouldn't object to adding code
> to deal with overlength identifies, but I'm not really sure I would
> choose truncation over reporting an error. But whatever it'd be, it'd
> be at that level, not at the lower (hash function) level.
Yeah, I'm now convinced that whatever we do about this, if we do anything,
needs to be at a higher code level. It's not hashname()'s job to prevent
use of overlength names. I'll go remove the Assert.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
