Searched hist:"75 ba6767" (Results 1 – 4 of 4) sorted by relevance
| /sqlite-3.40.0/test/ |
| H A D | vacuum5.test | 75ba6767 Wed Nov 02 14:50:19 GMT 2016 dan <[email protected]> Fix an issue that was causing the new database image to be assembled entirely
in heap memory when VACUUMing a database, even if it should use a temp file.
This could cause SQLITE_NOMEM errors when vacuuming very large databases on
32-bit systems.
FossilOrigin-Name: 3028845329c9b7acdec2ec8b01d00d782347454c
|
| /sqlite-3.40.0/src/ |
| H A D | vacuum.c | 75ba6767 Wed Nov 02 14:50:19 GMT 2016 dan <[email protected]> Fix an issue that was causing the new database image to be assembled entirely
in heap memory when VACUUMing a database, even if it should use a temp file.
This could cause SQLITE_NOMEM errors when vacuuming very large databases on
32-bit systems.
FossilOrigin-Name: 3028845329c9b7acdec2ec8b01d00d782347454c
|
| /sqlite-3.40.0/ |
| H A D | manifest.uuid | 75ba6767 Wed Nov 02 14:50:19 GMT 2016 dan <[email protected]> Fix an issue that was causing the new database image to be assembled entirely
in heap memory when VACUUMing a database, even if it should use a temp file.
This could cause SQLITE_NOMEM errors when vacuuming very large databases on
32-bit systems.
FossilOrigin-Name: 3028845329c9b7acdec2ec8b01d00d782347454c
|
| H A D | manifest | 75ba6767 Wed Nov 02 14:50:19 GMT 2016 dan <[email protected]> Fix an issue that was causing the new database image to be assembled entirely
in heap memory when VACUUMing a database, even if it should use a temp file.
This could cause SQLITE_NOMEM errors when vacuuming very large databases on
32-bit systems.
FossilOrigin-Name: 3028845329c9b7acdec2ec8b01d00d782347454c
|