[mjb]

Which features would you like to see the team build first? Which limits would you like to see lifted first?

Most of the limitations you can see in the documentation are things we haven't gotten to building yet, and it's super helpful to know what folks need so we can prioritize the backlog.

[avereveard]

indexes! vector, trigram and maybe geospatial. (some may be in by now I didn't follow the service as closely as others)

note, doesn't have to be pg_vector pg_trgm or PostGIS, just the index component even if it's a clean room implementation would make this way more useful.

[tomComb]

The lack of JSONB is what stopped me.

[loginatnine]

Views and foreign keys!

[mjb]

Thanks. The team's working on both. For views, do you need updatable views, or are read-only views sufficient?

[loginatnine]

For me it's RO views.

[tigy32]

I believe views were added to the preview a little while ago

edit from the launch: "With today’s launch, we’ve added support for AWS Backup, AWS PrivateLink, AWS CloudFormation, AWS CloudTrail, AWS KMS customer managed keys, and PostgreSQL views."

[mjb]

Correct: https://docs.aws.amazon.com/aurora-dsql/latest/userguide/wor...

[sgarland]

Why does it not support TRUNCATE?

[jashmatthews]

My understanding is the way Aurora DSQL distributes data widely makes bulk writes extremely slow/expensive. So no COPY, INSERT with >3k rows, TRUNCATE etc

[sgarland]

TRUNCATE is DROP TABLE + CREATE TABLE, it’s not a bulk delete. It bypasses the typical path for writes entirely.