# \[Self-hosted : supabase-DB\] NocoDB doesn’t recognize PK from Postgres

**URL:** <https://community.nocodb.com/t/self-hosted-supabase-db-nocodb-doesn-t-recognize-pk-from-postgres/2147>\
**Category:** Self-Host\
**Created:** [January 5, 2026, 3:40am UTC](https://community.nocodb.com/t/self-hosted-supabase-db-nocodb-doesn-t-recognize-pk-from-postgres/2147 "2026-01-05T03:40:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![eason](https://avatars.discourse-cdn.com/v4/letter/e/9fc348/32.png) [@eason](https://community.nocodb.com/u/eason)\
**Post date:** [January 5, 2026, 3:40am UTC](https://community.nocodb.com/t/self-hosted-supabase-db-nocodb-doesn-t-recognize-pk-from-postgres/2147/1 "2026-01-05T03:40:34Z")

</div>

Nocodb view. Can not edit. I’ve tried recreated base and restart docker, but still failed.

 ![image](https://canada1.discourse-cdn.com/flex011/uploads/nocodb/original/1X/8123e232422edabe2a0bc66de047fb6708a86f95.png)

supabase can edit, and have PK.

---

<div class="post-metadata">

**Author:** ![eason](https://avatars.discourse-cdn.com/v4/letter/e/9fc348/32.png) [@eason](https://community.nocodb.com/u/eason)\
**Post date:** [January 5, 2026, 3:48am UTC](https://community.nocodb.com/t/self-hosted-supabase-db-nocodb-doesn-t-recognize-pk-from-postgres/2147/2 "2026-01-05T03:48:13Z")

</div>

supabase works well.

 ![image](https://canada1.discourse-cdn.com/flex011/uploads/nocodb/original/1X/aeeaf7ef734f3664def041bf5c42da4035c15313.png)

---

<div class="post-metadata">

**Author:** ![Navi](https://avatars.discourse-cdn.com/v4/letter/n/3be4f8/32.png) [@Navi](https://community.nocodb.com/u/Navi)\
**Post date:** [January 8, 2026, 9:56am UTC](https://community.nocodb.com/t/self-hosted-supabase-db-nocodb-doesn-t-recognize-pk-from-postgres/2147/3 "2026-01-08T09:56:57Z")

</div>

Are you using the same credentials as in supabase with nocodb.

If so, can you confirm you have run the [metadata sync](https://nocodb.com/docs/product-docs/data-sources/sync-with-data-source).

My guess here, nocodb was connected to supabase before there was a primary key and after connecting primary key was created in supabase.

---

<div class="post-metadata">

**Author:** ![eason](https://avatars.discourse-cdn.com/v4/letter/e/9fc348/32.png) [@eason](https://community.nocodb.com/u/eason)\
**Post date:** [January 18, 2026, 1:52am UTC](https://community.nocodb.com/t/self-hosted-supabase-db-nocodb-doesn-t-recognize-pk-from-postgres/2147/4 "2026-01-18T01:52:15Z")

</div>

> [@Navi](#):
>
> supabase

I have to set the table owner to postgres to fix the issue, not sure why, thanks for the feedback