Glide Big Table Limitations Vs Postgres Limitations

[punnned]

We are starting work on an app that requires a large amount of rows.
Deciding between using Glide Big Tables or Postgres as a data source.

Questions:
Do they share the same limitations? e.g. rollup limitations on computed columns etc?

I see there is currently a ‘preview’ feature called “More computed columns in Glide Big Tables” - is this explicitly for Big Tables or does this apply for all ‘large data sources’ such as Postgres?

Are there any obvious ‘savings’ from a monthly syncs quota perspective of using Postgres Vs Glide Big Tables?

Thanks!

[ThinhDinh]

@punnned

Do they share the same limitations? e.g. rollup limitations on computed columns etc?

Here are their documented limitations at the moment.

@punnned

I see there is currently a ‘preview’ feature called “More computed columns in Glide Big Tables” - is this explicitly for Big Tables or does this apply for all ‘large data sources’ such as Postgres?

I’m not sure but they’re only documented for Big Tables at the moment.

@punnned

Are there any obvious ‘savings’ from a monthly syncs quota perspective of using Postgres Vs Glide Big Tables?