From 66a4a0b32db0773e2f0613c6f2236b871c3a24fc Mon Sep 17 00:00:00 2001 From: Eduardo Gurgel Date: Fri, 7 Aug 2026 10:00:53 +1200 Subject: [PATCH] fix(docs): realtime deletes can be surfaced and filtered (#48785) --- apps/docs/content/guides/realtime/postgres-changes.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/apps/docs/content/guides/realtime/postgres-changes.mdx b/apps/docs/content/guides/realtime/postgres-changes.mdx index 5094cdf3b20..e43943740d6 100644 --- a/apps/docs/content/guides/realtime/postgres-changes.mdx +++ b/apps/docs/content/guides/realtime/postgres-changes.mdx @@ -3438,7 +3438,7 @@ alter table -RLS policies are not applied to `DELETE` statements, because there is no way for Postgres to verify that a user has access to a deleted record. When RLS is enabled and `replica identity` is set to `full` on a table, the `old` record contains only the primary key(s). +RLS policies are not applied to `DELETE` statements, because there is no way for Postgres to verify that a user has access to a deleted record. @@ -3619,9 +3619,9 @@ await channel.Subscribe(); ## Limitations -### Delete events are not filterable +### Delete events -You can't filter Delete events when tracking Postgres Changes. This limitation is due to the way changes are pulled from Postgres. +You can only filter Delete events when tracking Postgres Changes if the table has the `replica identity` set to `full`. See [Receiving old records](#receiving-old-records). ## Scaling Postgres Changes