#2124 (ok 2.9.0) Cannot export compressed SQL

[d11]

I am using the following:

phpMyAdmin 2.8.0.3
Apache 2.0.40
PHP 4.2.2
MySQL 3.23.58

I cannot export any compressed SQL using SSL. I'm not
sure if not using SSL will work, but I don't want to
enter my password unsecured. I've tried exporting ZIP,
GZ, and BZIP and none work. All that is exported is a
192 byte compressed file (zip, gz, bz) and when I try
to open it in WinRAR it says "c:\dbname.sql.gz The
archive is either in unknown format or damaged."

Exporting just a plain text .sql file works though.
I've had this problem since version 2.7.x at least.

[Michal Čihař]

Logged In: YES
user_id=192186

BTW: do uncompressed exports work for you?

[d11]

Logged In: YES
user_id=1510647

Yes, uncompressed exports work fine.

BTW, sorry about the delayed response as I changed to a new
computer and was transferring/setting up.

[Michal Čihař]

Logged In: YES
user_id=192186

I'm a bit out of ideas.

Can you try to find value that will make it work on line
mentioned sooner?

($memory_limit /= 3;)

Just increase it and sometimes it should start to work.

[d11]

Logged In: YES
user_id=1510647

I changed the $memory_limit /= 3; to $memory_limit /= 6; and
now I can export the large database to gzip successfully.

Zip and BZip don't seem to work, but at least one
compression method does now which is good. Thanks very much
for your help nijel.

[Michal Čihař]

Logged In: YES
user_id=192186

bzip should also work, but maybe it is even more memory
hungry so you might need even larger value.

Zip won't work as we need to create whole zip file in memory.

[Michal Čihař]

Logged In: YES
user_id=192186

I changed code to contain / 8, which will hopefully be enough.

[d11]

Logged In: YES
user_id=1510647

I'm sure you're correct about bzip being more memory
intensive than gzip.

Since gzip is working for me that's good enough. Thanks again.

[Michal Čihař]

Logged In: YES
user_id=192186

Please leave entry open till version fixing this is released.

[Giles]

Logged In: YES
user_id=838206
Originator: NO

Hi, was there a resolution to this issue?

I have been having problems exporting a large-ish database (~55mb) and do not really want to pump the memory limit on PHP up that high since other users on the box could abuse it.

Where PMA detects that the memory limit is smaller than ~90% of the DB aggregate size, could it perhaps output raw SQL directly to the output (as opposed to storing it in memory)? E.g. as it reads a row from the DB, it sends the data to the output, rather than storing it in a large string or array which ends up the same size as the DB.

[Michal Čihař]

Logged In: YES
user_id=192186
Originator: NO

It does exactly this when you have enabled CompressOnFly (what is default). The problem here was AFAIK with buffer size we can use while doing on fly compression (because we need to compress some bigger blocks), which was too big to actually fit within the limits.