On Fri, 28 Sep 2001, [iso-8859-1] Lo�c wrote:
Hi Steve & list!
The problem you faced are related to two kinds of improvements of the 2.2.0 release :
- the compressing features;
- the output buffering feature.
There is only one way to lower memory usage IMHO: to display dump statements one by one. It means that we should stop output buffering while building dump (easy to do) and create a temporary text file on the server that will contain the dump statements before to be compressed if compression mode is required.
It means we have to setup a directory that is readable and writable by the script where to put these temporary files.
That is not an option, as it can create more security holes, and I believe it will not work in same cases with PHP in safe mode.
Would there possibly be a way, that we can compress the dump statements one by one as we send them? Possibly an implicit flush when we are using gzip'd output buffering?