This entails having a max_chunk parameter, currently hard-wired to
match default fetch_chunksize, but will become configurable.

In a perfect world, max_chunk would be automatically set to the
current value of fetch_chunksize -- setting it larger would be
unsafe. But since we can't read cache_param without violating
the API, we can only warn users not to do that. *sigh*