track_activity_query_size change from default 1024 to higher values like 4096+

Are there some know performance or other side effect(s) when changing track_activity_query_size from 1024 to 4096+ size. Obvious requirement will be on the increase of memory (4+ times) to store the query string.
--