# Glide Big Table Limitations Vs Postgres Limitations

**URL:** <https://community.glideapps.com/t/glide-big-table-limitations-vs-postgres-limitations/72486>\
**Category:** Ask for Help\
**Created:** [April 11, 2024, 12:37pm UTC](https://community.glideapps.com/t/glide-big-table-limitations-vs-postgres-limitations/72486 "2024-04-11T12:37:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![punnned](https://avatars.discourse-cdn.com/v4/letter/p/41988e/32.png) [@punnned](https://community.glideapps.com/u/punnned)\
**Post date:** [April 11, 2024, 12:37pm UTC](https://community.glideapps.com/t/glide-big-table-limitations-vs-postgres-limitations/72486/1 "2024-04-11T12:37:15Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [April 11, 2024, 11:21pm UTC](https://community.glideapps.com/t/glide-big-table-limitations-vs-postgres-limitations/72486/2 "2024-04-11T23:21:40Z")

</div>

> [@punnned](#):
>
> Do they share the same limitations? e.g. rollup limitations on computed columns etc?

Here are their documented limitations at the moment.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/4/0/4059bbb0be29c7e39520823435eb2cecf06b984a.png)

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/6/5/6542c50e82b04bf17693b6e2b2aa16d8f33b802b.png)

> [@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?

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/f/c/fc0a38045eb80231e5a5f6d6b624662bb60621c2.png)

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/7/a/7a0097d0a564bb0270f54cf9ca3d631e43abd542.png)

---

<div class="post-metadata">

**Author:** ![Benjamin\_Sabbah](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/benjamin_sabbah/32/19379_2.png) [@Benjamin\_Sabbah](https://community.glideapps.com/u/Benjamin_Sabbah)\
**Post date:** [November 5, 2024, 9:21am UTC](https://community.glideapps.com/t/glide-big-table-limitations-vs-postgres-limitations/72486/3 "2024-11-05T09:21:17Z")

</div>

Hi,

Are 100 rows limitations for computed columns still en effect with Glide Big Tables ?