According to the Mysql documentation 5.7 about the limit in table size, says:
C.10.3 Table size limits
The maximum effective table size for Mysql databases
is usually determined by operating system restrictions on
file sizes, not internal Mysql boundaries. To
get up-to-date information on file size limits
of the operating system, see the documentation specific to your
operating system.
Windows users, note that FAT and VFAT (FAT32) are not considered
suitable for production use with Mysql. Use NTFS instead.
If you encounter a complete table error, there are several reasons why
which may have occurred:
The disk may be full.
- You are using Innodb in the tables and ran out of space in an Innodb table space file. The maximum size of the tablespace
is also the maximum size for a table.
- Generally, the sharing of tables in multiple files tablespace is recommended for tables with size greater than 1 TB.
- You have reached an operating system file size limit. For example, you are using Myisam in the tables on a
operating system that supports files up to 2GB in size and you
reached this limit for data file or index file.
- You are using a Myisam in the table and the space required for the table exceeds what is allowed by the internal pointer size. Myisam
allows data and index files to grow up to 256TB per
standard, but this limit can be changed to the maximum size
65,536 TB allowed (256 7 - 1 bytes).
That is, the problem is not in Mysql. Maybe if you post some code snippets we can help you better.
It doesn’t seem to be a problem with the storage capacity, since 487 is a relatively low number. Each record takes up a lot of memory?
– Woss
No, it’s text only, I currently have 543 records with 240.0KiB of storage.
– Pedro
So really the problem isn’t the bank’s capacity. Possibly it’s import failure or something like that. See if you can [Edit] the question and give more details of how you are doing the data export and import.
– Woss
Okay, I’ll go into detail, let me know if I’m performing the right way.
– Pedro