Hi Steve & list!
The problem you faced are related to two kinds of improvements of the 2.2.0 release : 1) the compressing features; 2) 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.
Loïc
______________________________________________________________________________ ifrance.com, l'email gratuit le plus complet de l'Internet ! vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... http://www.ifrance.com/_reloc/email.emailif
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?
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.
What you think about crete a phpMyAdmin database and use that for temporary data. This also can hold configuration variables, query bookmarks and translation strings.
Loïc
Saludos Edu
On Fri, 28 Sep 2001, Eduardo Cintas wrote:
What you think about crete a phpMyAdmin database and use that for temporary data. This also can hold configuration variables, query bookmarks and translation strings.
Because that will not always be an option. In some cases I run phpMyAdmin as just a user level, to administer only a single database, that I have access to, and I don't have access to any other databases, nor do I have permissions to CREATE/DROP TABLE.
-
Eduardo Cintas -
Loïc -
Robin Johnson