track_activity_query_size

Is there a performance downside to setting track_activity_query_size to
a significantly larger value than the default 1024 (say 10240), given
that there's plenty of memory to spare?

cheers

andrew