Merge lp:~massimo-siani/mariadb-java-client/maxseqno into lp:mariadb-java-client
Proposed by
Massimo Siani
Status: | Merged |
---|---|
Merge reported by: | Massimo Siani |
Merged at revision: | not available |
Proposed branch: | lp:~massimo-siani/mariadb-java-client/maxseqno |
Merge into: | lp:mariadb-java-client |
Diff against target: |
12 lines (+1/-1) 1 file modified
src/main/java/org/mariadb/jdbc/internal/common/packet/PacketOutputStream.java (+1/-1) |
To merge this branch: | bzr merge lp:~massimo-siani/mariadb-java-client/maxseqno |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Maria-captains | Pending | ||
Review via email:
|
Commit message
Increase MAXSEQNO to avoid "MySQL protocol limit reached, you cannot send more than 4GB of data"
Description of the change
By Polystar:
Increasing MAX_SEQNO to avoid "MySQL protocol limit reached, you cannot send more than 4GB of data" when using LOAD DATA INFILE with big sizes. The MAX_SEQNO was wrong, causing it to be impossible to send queries of larger since than about 2MB (each packet is 8192 bytes multiplied with 255 is 2088960 bytes). I just increased the MAX_SEQNO to a very high value, not sure if the Mysql/MariaDB server actually can handle it.
To post a comment you must log in.