From 2cc1aa4493daf2905838720d9d36896f7b095a4c Mon Sep 17 00:00:00 2001 From: Chris Chinchilla Date: Tue, 5 May 2026 14:38:36 +0200 Subject: [PATCH] Apply suggestions from code review Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --- apps/docs/content/guides/telemetry/logs.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/apps/docs/content/guides/telemetry/logs.mdx b/apps/docs/content/guides/telemetry/logs.mdx index 7bd8719193..c8957dd246 100644 --- a/apps/docs/content/guides/telemetry/logs.mdx +++ b/apps/docs/content/guides/telemetry/logs.mdx @@ -213,10 +213,10 @@ show log_min_messages; Note that `LOG` is a higher level than `WARNING` and `ERROR`, so if your level is set to `LOG`, you will not see `WARNING` and `ERROR` messages. -### Limits and Caveats +### Limits and caveats -- PostgreSQL log events on the Supabase Platform are limited to 100,000 characters. If a log event exceeds this limit, it will be truncated. This does not apply to self-hosting. -- Internal connection logs to PostgreSQL within the Supabase Platform by internal services are not logged. This does not apply to self-hosting. +- Postgres log events on the Supabase Platform are limited to 100,000 characters. If a log event exceeds this limit, it will be truncated. This does not apply to self-hosting. +- Internal connection logs to Postgres within the Supabase Platform by internal services are not logged. This does not apply to self-hosting. ## Logging realtime connections