[MCOL-3543] Multiple insert from select problems Created: 2019-10-04 Updated: 2023-03-06 Resolved: 2023-03-06 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | N/A |
| Affects Version/s: | 1.2.5 |
| Fix Version/s: | Icebox |
| Type: | Bug | Priority: | Major |
| Reporter: | Patrick LeBlanc (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Ubuntu 18 |
||
| Description |
|
Starting from the 50g DBT3 DB. Been attempting to combine lineitem & orders -> lineorders for benchmarking reasons. Pretty straightforward. Ran into three problems and one debatable problem 2) I added tmp space, then tried again. I got a nonsensical error message "ERROR 1030 (HY000): Got error -1 "Internal error < 0 (Not system error)" from storage engine Columnstore". This apparently is what we return when the table is locked (I didn't know it was locked, and this msg didn't help). 3) After removing the table lock, I ran it again. It seems to have succeeded, but not told mysqld of that fact. So, the mysql client just sat there. Hitting ctrl-c to get out of the client thankfully did not roll the whole thing back. Getting the row count of the new table gives the right result. 4) (debatable) insert-select goes through the mariadb server, which generates an enormous binlog for this (45GB). I'm rarely on the user side of a DB; not sure if it's supposed to do that, or if we can disable it for this kind of operation. I imagine there must be a configurable limit on how large it can get before it starts rolling off data. This one is mainly on me; I need to find out what the options are for the user to avoid an out-of-space error b/c of the binlog. The create table stmt for lineorder: The insert-select stmt: |