History[02]

C-Store is an academic project led by Michael Stonebraker and Daniel Abadi, involving people from Brown University, Brandeis University, MIT and the University of Massachusetts Boston. It was later commercialized into Vertica.

Concurrency Control[03]

The system maintains a distributed lock table. Deadlock is resolved via timeouts by aborting one of the deadlocked transactions. (I think this means deadlock detection?)

Data Model[03]

Logically, C-Store supports the standard relational data model, where a database contains a collection of tables and a table contains a collection of attributes.

Foreign Keys[03]

Indexes[03]

Despite the different possible encoding schemes of a column (e.g. RLE, bit-map encoding, or block-oriented delta encoding), they all use B-tree indexes. The system also stores join indices to stitch together all records in a table from its different columns (projections). Since a column which is ordered by another column in the same projection and contains few distinct values is encoded using bit-map encoding plus RLE, the paper also mentioned their extensive use of bitmap indexes.

Isolation Levels[03]

(The paper talks in detail about their support for snapshot isolation, but does not mention if they support other isolation level ...)

Joins

(found in their source code)

Logging[03]

"We use logical logging (as in ARIES), since physical logging would result in many log records, due to the nature of the data structures in WS." (But I believe ARIES log is physical logging? So confused ...)

Query Compilation

Query Execution[03]

Query Interface[04][03]

Logically, users interact with C-Store in SQL, with standard SQL semantics.

Storage Architecture[05][03]

Each column is stored as a separate file containing a list of 64K blocks, each packing as many values as possible.

Storage Model[03]

As the name suggests, C-Store is all about column store ... Interestingly, both the read-optimized store component and the update/insert-oriented writable store component adopt the column store architecture.

Stored Procedures

(I don't think they mention it, so I guess it's a no?)

System Architecture[03]

The architecture was designed anticipating an environment of grid computers, containing large number of nodes each with private disk and memory. The data is horizontally partitioned across the disks of the nodes.

Views

(found in their source code 'write store materialized view')