#ifndef __BLOB_MANAGER_H #define __BLOB_MANAGER_H #include #include BEGIN_C_DECLS /** @file blobManager - Provides blob handling @todo Set range?? Plan for modularity: Exactly one blob manager per storeFile. Blob manager interacts with page manger via page manager's public api. Blob updates work as follows: (1) A transaction obtains an exclusive write lock on a blob (not implemented yet.) (2) When it requests a write, the blob it writes to is added to a data structure that lists all dirty blobs by transaction, and the page containing the blob entry is updated. (The fd bit in the record is flipped, and the LSN is updated.) The write to the blob store is not flushed to disk. (3) All subsequent writes to the same blob just update the backing file. (4) On commit and rollback, the data structure containing the xid's dirty blobs is destroyed. (5) recovery2.c handles the restoration of the fd bits using physical logging (this is automatic, since we use Tset() calls to update the records.) @todo Should the tripleHash be its own little support library? */ /** Read the blob from the recordid rid into buf. */ void readBlob(int xid, recordid rid, void * buf); /** Write the contents of buf to the blob in recordid rid. */ void writeBlob(int xid, lsn_t lsn, recordid rid, const void * buf); /** Atomicly (with respect to recovery) make the dirty version of the blob the primary copy and mark it not-dirty. */ void commitBlobs(int xid); /** Revert the blob to the last clean version. */ void abortBlobs(int xid); typedef struct { unsigned offset; unsigned long size; unsigned fd : 1; } blob_record_t; /** Allocate a blob of size blobSize. @todo This function does not atomically allocate space in the blob file. */ recordid allocBlob(int xid, lsn_t lsn, size_t blobSize); void openBlobStore(); void closeBlobStore(); END_C_DECLS #endif