From 45397a2176b49e288e3acb02809fbe432f35dfdb Mon Sep 17 00:00:00 2001 From: TzeYiing Date: Tue, 5 May 2026 17:47:41 +0800 Subject: [PATCH] docs: add documentation for postgres logs --- apps/docs/content/guides/telemetry/logs.mdx | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/apps/docs/content/guides/telemetry/logs.mdx b/apps/docs/content/guides/telemetry/logs.mdx index e8f30e05d8..7bd8719193 100644 --- a/apps/docs/content/guides/telemetry/logs.mdx +++ b/apps/docs/content/guides/telemetry/logs.mdx @@ -213,6 +213,11 @@ 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 + +- 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. + ## Logging realtime connections Realtime doesn't log new WebSocket connections or Channel joins by default. Enable connection logging per client by including an `info` `log_level` parameter when instantiating the Supabase client.