Re: NAMEDATALEN configuration option patch

Peter Eisentraut <peter_e@gmx.net> writes:
> Bill McGonigle writes:
>> The only possible problem I forsee is if an external program includes
>> "postgres_ext.h" and there is a name collision with something in
>> config.h.

> That is precisely the reason why this cannot be done that way.

I'm fairly uncomfortable with the thought of making NAMEDATALEN so
easily twiddle-able.  The problem is precisely that the value does
propagate into client programs, and thus that there are going to be
interoperability risks between clients with one setting and servers
with another.  I don't like the idea of people choosing random values
at configure time without thinking hard about what they're doing.

I would be in favor of raising the standard value to 64 (from the
current 32) in the next major release, 7.2.  That should be enough
to damp down the complaints ... IMHO anyway ...

            regards, tom lane