Skip to content

The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.

chore(studio): remove [edge] label from logs search suggestions (#42944)

kemal.earth48e4140202d0
diff --git a/apps/docs/content/guides/self-hosting/restore-from-platform.mdx b/apps/docs/content/guides/self-hosting/restore-from-platform.mdx
index 7b300083aec..71546c9397a 100644
--- a/apps/docs/content/guides/self-hosting/restore-from-platform.mdx
+++ b/apps/docs/content/guides/self-hosting/restore-from-platform.mdx
@@ -100,14 +100,14 @@ SELECT * FROM pg_extension;
The database dump includes your schema, data, roles, RLS policies, database functions, triggers, and `auth.users`. However, several things require separate configuration on your self-hosted instance:
-| Requires manual setup | How to configure |
-| --- | --- |
-| JWT secrets and API keys | Generate new ones and update `.env` |
+| Requires manual setup | How to configure |
+| ------------------------------------------- | ------------------------------------------------- |
+| JWT secrets and API keys | Generate new ones and update `.env` |
| Auth provider settings (OAuth, Apple, etc.) | Configure `GOTRUE_EXTERNAL_*` variables in `.env` |
-| Edge functions | Manually copy to your self-hosted instance |
-| Storage objects | Transfer separately (not covered in this guide) |
-| SMTP / email settings | Configure `SMTP_*` variables in `.env` |
-| Custom domains and DNS | Point your DNS to the self-hosted server |
+| Edge functions | Manually copy to your self-hosted instance |
+| Storage objects | Transfer separately (not covered in this guide) |
+| SMTP / email settings | Configure `SMTP_*` variables in `.env` |
+| Custom domains and DNS | Point your DNS to the self-hosted server |
## Auth considerations
@@ -155,7 +155,7 @@ Keeping your self-hosted configuration [up to date](https://github.com/supabase/
If the restore fails because an extension isn't available, check whether it's supported on your self-hosted Postgres version. You can list available extensions with:
```sql
-SELECT * FROM pg_available_extensions;
+select * from pg_available_extensions;
```
### Connection refused
diff --git a/apps/docs/content/troubleshooting/realtime-project-suspended-for-exceeding-quotas.mdx b/apps/docs/content/troubleshooting/realtime-project-suspended-for-exceeding-quotas.mdx
index a3ff1431754..fa700d13e96 100644
--- a/apps/docs/content/troubleshooting/realtime-project-suspended-for-exceeding-quotas.mdx
+++ b/apps/docs/content/troubleshooting/realtime-project-suspended-for-exceeding-quotas.mdx
@@ -36,6 +36,7 @@ In most cases, quota overages are accidental rather than intentional:
## What to do if your project is suspended
1. **Open a support ticket**: [Contact support](/dashboard/support/new) and include:
+
- Your project reference ID
- A description of your Realtime use case (what features use Broadcast, Presence, or Postgres Changes)
- An estimate of your expected concurrent connections and message throughput
diff --git a/apps/studio/components/ui/DataTable/DataTableFilters/DataTableFilterCommand.tsx b/apps/studio/components/ui/DataTable/DataTableFilters/DataTableFilterCommand.tsx
index 7f4edbb1eba..b76d1926362 100644
--- a/apps/studio/components/ui/DataTable/DataTableFilters/DataTableFilterCommand.tsx
+++ b/apps/studio/components/ui/DataTable/DataTableFilters/DataTableFilterCommand.tsx
@@ -382,11 +382,13 @@ function CommandItemSuggestions<TData>({ field }: { field: DataTableFilterField<
case 'checkbox': {
return (
<span className={cn(className)}>
- {getFacetedUniqueValues
- ? Array.from(getFacetedUniqueValues(table, value)?.keys() || [])
- .map((value) => `[${value}]`)
- .join(' ')
- : field.options?.map(({ value }) => `[${value}]`).join(' ')}
+ {field.options && field.options.length > 0
+ ? field.options.map(({ value }) => `[${value}]`).join(' ')
+ : getFacetedUniqueValues
+ ? Array.from(getFacetedUniqueValues(table, value)?.keys() || [])
+ .map((value) => `[${value}]`)
+ .join(' ')
+ : null}
</span>
)
}
diff --git a/apps/www/_blog/2026-02-04-hydra-joins-supabase.mdx b/apps/www/_blog/2026-02-04-hydra-joins-supabase.mdx
index 346d5f61282..bcddff58aaa 100644
--- a/apps/www/_blog/2026-02-04-hydra-joins-supabase.mdx
+++ b/apps/www/_blog/2026-02-04-hydra-joins-supabase.mdx
@@ -40,7 +40,7 @@ This effort includes:
### Next Steps for Hydra
-Everything will stay open source. We'll help [MotherDuck](https://motherduck.com/) with `pg_duckdb` contributions and take over the maintenance of Hydra's existing repos. We will work in the open as we develop the Open Warehouse Architecture and the broader Postgres + Analytics vision.
+Everything will stay open source. We'll help [MotherDuck](https://motherduck.com/) with `pg_duckdb` contributions and take over the maintenance of Hydra's existing repos. We will work in the open as we develop the Open Warehouse Architecture and the broader Postgres + Analytics vision.
## Join us to build the Open Warehouse