DBMS storage management for non-volatile memory

A computer-implemented method, comprising:

• receiving an instruction to create a data block associated with a portion of a database table in a non-volatile memory system;
• in response to the instruction to create the data block, creating a file associated with the data block in the non-volatile memory system;
• receiving an instruction to commit the data block;
• in response to the instruction to commit the data block, flushing data associated with the data block to the file in the non-volatile memory system, renaming the file to remove the indication that the data block is a temporary block, and updating the entry in the data block map to indicate that the data block is a committed block;
• receiving an instruction to delete the data block;
• and
• in response to the instruction to delete the data block, creating an entry in a tombstone block map comprising an identifier of the data block, and create a tombstone file, where a directory path of the tombstone file indicates the data block and a current savepoint version.

A non-transitory computer-readable medium storing program code, the program code executable by a computer system to cause to the computer system to:

• receive an instruction to create a data block associated with a portion of a database table in a non-volatile memory system;
• in response to the instruction to create the data block, create a file associated with the data block in the non-volatile memory system, where a filename of the file comprises an indication that the data block is a temporary block;
• create an entry in a data block map table indicating that the data block is a temporary block;
• receive an instruction to commit the data block;
• in response to the instruction to commit the data block, flush data associated with the data block to the file in the non-volatile memory system, rename the file to remove the indication that the data block is a temporary block, and update the entry in the data block map to indicate that the data block is a committed block;
• receive an instruction to delete the data block;
• and
• in response to the instruction to delete the data block, create an entry in a tombstone block map comprising an identifier of the data block, and create a tombstone file, where a directory path of the tombstone file indicates the data block and a current savepoint version.