9 ms·

Early dsql had some weird limits I think - anyone actually using in production with feedback on current corners and limits?

Marbling4581 1y ago
I don't use it, but have been keeping an eye on it. At launch, they limited the number of affected tuples to 10000, including tuples in secondary indexes. They recently changed this limit to: > A transaction cannot modify more than 3,000 rows. The number of secondary indexes does not influence this number. This limit applies to all DML statements (INSERT, UPDATE, DELETE). There are a lot of other (IMO prohibitive) restrictions listed in their docs. https://docs.aws.amazon.com/aurora-dsql/latest/userguide/working-with-postgresql-compatibility-unsupported-features.html https://docs.aws.amazon.com/aurora-dsql/latest/userguide/wor...
pzduniak 1y ago
Who would use Preview products in production? I'm building out some software that would fit perfectly into the constraints set for DSQL, but I realistically can't commit to something with no pricing / guarantees.
- EwanToo 1y ago
  This blog post appears to be part of the scheduled launch marketing, it's now generally available https://aws.amazon.com/blogs/aws/amazon-aurora-dsql-is-now-generally-available/ https://aws.amazon.com/blogs/aws/amazon-aurora-dsql-is-now-g...
mjb 1y ago
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 1y ago
  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.
- loginatnine 1y ago
  Views and foreign keys!
  - mjb 1y ago
    Thanks. The team's working on both. For views, do you need updatable views, or are read-only views sufficient?
    - loginatnine 1y ago
      For me it's RO views.
      - tigy32 1y ago
        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 1y ago
        Correct: https://docs.aws.amazon.com/aurora-dsql/latest/userguide/working-with-postgresql-compatibility-supported-sql-subsets.html#create-view https://docs.aws.amazon.com/aurora-dsql/latest/userguide/wor...
- tomComb 1y ago
  The lack of JSONB is what stopped me.
- 1y ago
loevborg 1y ago
Which ones? It seems eminently usable from the outside now, at least for greenfield work. The subset of Postgres it supports is most of good/core/essential Postgres. (But I haven't tried it)

Marbling4581 1y ago

I don't use it, but have been keeping an eye on it. At launch, they limited the number of affected tuples to 10000, including tuples in secondary indexes. They recently changed this limit to: > A transaction cannot modify more than 3,000 rows. The number of secondary indexes does not influence this number. This limit applies to all DML statements (INSERT, UPDATE, DELETE). There are a lot of other (IMO prohibitive) restrictions listed in their docs. https://docs.aws.amazon.com/aurora-dsql/latest/userguide/working-with-postgresql-compatibility-unsupported-features.html https://docs.aws.amazon.com/aurora-dsql/latest/userguide/wor...

pzduniak 1y ago

Who would use Preview products in production? I'm building out some software that would fit perfectly into the constraints set for DSQL, but I realistically can't commit to something with no pricing / guarantees.

EwanToo 1y ago
This blog post appears to be part of the scheduled launch marketing, it's now generally available https://aws.amazon.com/blogs/aws/amazon-aurora-dsql-is-now-generally-available/ https://aws.amazon.com/blogs/aws/amazon-aurora-dsql-is-now-g...

mjb 1y ago

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 1y ago
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.
loginatnine 1y ago
Views and foreign keys!
- mjb 1y ago
  Thanks. The team's working on both. For views, do you need updatable views, or are read-only views sufficient?
  - loginatnine 1y ago
    For me it's RO views.
    - tigy32 1y ago
      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 1y ago
        Correct: https://docs.aws.amazon.com/aurora-dsql/latest/userguide/working-with-postgresql-compatibility-supported-sql-subsets.html#create-view https://docs.aws.amazon.com/aurora-dsql/latest/userguide/wor...
tomComb 1y ago
The lack of JSONB is what stopped me.
1y ago

loevborg 1y ago

Which ones? It seems eminently usable from the outside now, at least for greenfield work. The subset of Postgres it supports is most of good/core/essential Postgres. (But I haven't tried it)