Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> Maybe I'm just a Luddite, but I've never understood what autoheader
>> buys us that's worth the trouble of conforming to its restrictions.
> We wouldn't have to edit the config.h file by hand whenever some editing
> of configure.in
Tom Lane writes:
> Maybe I'm just a Luddite, but I've never understood what autoheader
> buys us that's worth the trouble of conforming to its restrictions.
We wouldn't have to edit the config.h file by hand whenever some editing
of configure.in occurs. That's all, but I'm not aware of any real
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> I want to make pg_config.h.in be automatically generated by autoheader
> so we don't have to edit it by hand, but there is a lot of stuff in
> pg_config.h.in that isn't directly generated by configure, so it needs
> to be moved elsewhere.
Maybe I'm ju
I want to make pg_config.h.in be automatically generated by autoheader
so we don't have to edit it by hand, but there is a lot of stuff in
pg_config.h.in that isn't directly generated by configure, so it needs
to be moved elsewhere.
Here's what I want to do:
Move DEF_NBUFFERS and DEF_MAXBACKENDS
