Re: set_config(‘search_path’) does not truncate names over 63 bytes, unlike SET

Hi Daniel,

> This is the only possibility IMHO. Is there a case where setting a
> longer value than what SET allows will be useful for anything?

I don't think so. A schema name over 63 bytes is never useful, since
the lookup only uses the first 63 bytes. But SET truncates each name,
not the list. A SET search_path with 500 names of 63 bytes is about
32kB, and it drops the connection the same way. So a limit per name is
not enough.

So 3 changes in the 0001
1. It limits every GUC_REPORT because extension can use this flag to
shoot themself in their foot.
2. It handles client -> server encoding conversion by
MAX_CONVERSION_GROWTH
3. Move the magic number 30000 to a #define.

0002 is an optional test.

Thanks,
Shihao