[MaxGanzII]

In my view, AWS docs (and support and so on) obfuscate everything which is not a strength; they cannot be trusted, not ever.

Redshift is a sorted relational database and as such it provides the performance necessary to handle Big Data when and only operated correctly, which is to say, when the sorting orders of the tables are correct for the queries being issued on those tables.

If you start talking as the quotes here do about "extremely complex SQL" it is going to be utterly impractical to operate Redshift correctly; it's impossibly complicated.

When operated incorrectly, Redshift has the same performance profile as good old Postgres, except you have the cluster rather than a single node.

The cluster is an expensive way to get 10x or 100x performance, but if you have Big Data, you need a LOT more performance than this - you need sorting, with the staggering efficiency gains it brings - but sorting only works when operated correctly.

The docs from AWS here are, in my view, utterly misleading and are dangerous to readers.

[the_af]

Oh, agreed. We use Redshift in production and you are absolutely right about its pitfalls and downsides.

Still, Athena is for S3 and is not a relational database engine, with all that this means. Redshift is one. That was my point.