Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Actual binary data are send using COM_STMT_SEND_LONG_DATA when using server prepare.
Actual implementation has 2 issues :
- Stream data are stored in an internal buffer, not send directly to socket.
- There is no max_allowed_packet size check to return a good client error. (COM_STMT_RESET must be called prior to throwing exception)
This cause unneeded use of memory, leading to OOM error, if stream size is really important.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
Actual binary data are send using COM_STMT_SEND_LONG_DATA when using server prepare.
Actual implementation has 2 issues : - Stream data are stored in an internal buffer, not send directly to socket. - There is no max_allowed_packet size check to return a good client error. This cause unneeded use of memory, leading to OOM error, if stream size is really important. |
Actual binary data are send using COM_STMT_SEND_LONG_DATA when using server prepare.
Actual implementation has 2 issues : - Stream data are stored in an internal buffer, not send directly to socket. - There is no max_allowed_packet size check to return a good client error. (COM_STMT_RESET must be called prior to throwing exception) This cause unneeded use of memory, leading to OOM error, if stream size is really important. |
| Status | Open [ 1 ] | Confirmed [ 10101 ] |
| Status | Confirmed [ 10101 ] | In Progress [ 3 ] |
| Component/s | Other [ 12201 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |
| Workflow | MariaDB v3 [ 79848 ] | MariaDB v4 [ 128339 ] |