I guess I have always thought of a transaction as an ACID-compliant concept and "transactional database" to refer to a DB that supports transactions[1]. To tha

I guess I have always thought of a transaction as an ACID-compliant concept and "transactional database" to refer to a DB that supports transactions[1]. To that end, I always thought of OLTP vs. OLAP model and engine optimizations to be more or less orthogonal to whether or not a DB is transactional. I would even suggest that the inclusion of transactions in Redshift as justification for my seemingly unconventional view: > Some PostgreSQL features that are suited to smaller-scale OLTP processing, such as secondary indexes and efficient single-row data manipulation operations, have been omitted to improve performance.[2] But who knows, maybe I am barking up the wrong tree so-to-speak. [1] https://en.wikipedia.org/wiki/Database_transaction#Transactional_databases https://en.wikipedia.org/wiki/Database_transaction#Transacti... [2] http://docs.aws.amazon.com/redshift/latest/dg/c_redshift-and-postgres-sql.html http://docs.aws.amazon.com/redshift/latest/dg/c_redshift-and...