Postgres Changes gets AND filters, new operators, and column selection

Summary

Postgres Changes now supports filters composed across multiple columns, additional operators, and column selection for subscriptions over Postgres tables. It can receive insert, update, and delete events over WebSockets, while comma-separated conditions or the postgresChangesFilter builder combine conditions with AND. New operators include like, ilike, is, match, imatch, isdistinct, and negated forms, while selected payloads always include the table's primary key. Column selection is opt-in, requires @supabase/supabase-js 2.109.0 or newer, and columns must be selectable by the subscribing role; Row Level Security still applies. These changes can lower billable usage because rejected events avoid messages per subscriber and trimmed payloads send fewer egress bytes, although DELETE events carry only the primary key and OR composition is unsupported.

Takeaways

1. 1

   Comma-separated filters and chained postgresChangesFilter conditions use AND composition; OR composition is not supported.

2. 2

   Column selection requires @supabase/supabase-js 2.109.0 or newer, and every listed column must be selectable by the subscribing role.

3. 3

   Rejected events save a message per subscriber, while selected payloads reduce egress bytes; DELETE events carry only the row's primary key, so column filters cannot be evaluated on deletes.