From ef05df1f61ca49a9b8d451333bdc1e13cca8a731 Mon Sep 17 00:00:00 2001
From: Marc Delisle <marc@infomarc.info>
Date: Fri, 25 Jan 2002 17:35:46 +0000
Subject: [PATCH] compressed dumps

---
 ChangeLog          |  3 +++
 Documentation.html | 11 +++++++++++
 2 files changed, 14 insertions(+)

diff --git a/ChangeLog b/ChangeLog
index bee04e053..4fcd21cc8 100755
--- a/ChangeLog
+++ b/ChangeLog
@@ -5,6 +5,9 @@ phpMyAdmin - Changelog
 $Id$
 $Source$
 
+2002-01-25  Marc Delisle  <lem9@users.sourceforge.net>
+	* Documentation.html: FAQ about compressed dumps
+
 2002-01-25  Loïc Chapeaux  <lolo@phpheaven.net>
 	* lang/bulgarian-*.inc.php3, japanese.inc.php3: updated thanks to
 	  Georgi Georgiev <chutz at chubaka.homeip.net>.
diff --git a/Documentation.html b/Documentation.html
index bbff69443..9505f76be 100755
--- a/Documentation.html
+++ b/Documentation.html
@@ -1134,6 +1134,17 @@
     logs in again.
 </p>
 
+<p>
+    <b>When dumping a large table in compressed mode, I get a memory limit
+       error or a time limit error.</b>
+    <br />
+    As of version 2.2.4, we build the compressed dump in memory, so large
+    tables dumps may hang.  The only alternative we can think about (using
+    system calls to mysqldump then gzip or bzip2) would not be applicable
+    in environments where PHP is in safe mode: access to system programs
+    is limited by the system administrator, and time limit is enforced.
+</p>
+
 <h3>[ISPs]</h3>
 <p>
     <b>I'm an ISP. Can I setup one central copy of phpMyAdmin or do I need to