---
title: "Postgres Changes gets AND filters, new operators, and column selection"
url: https://daily.dev/posts/postgres-changes-gets-and-filters-new-operators-and-column-selection-ejffdwnv1
source_url: https://supabase.com/blog/postgres-changes-filters-and-column-selection
type: article
source: "Supabase"
published: 2026-08-05T14:40:29.002Z
updated: 2026-08-24T06:52:46.953Z
tags: ["backend", "postgresql", "supabase", "websocket"]
reading_time: 3
upvotes: 32
comments: 3
language: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

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

**[Supabase](https://daily.dev/sources/supabase)** · 3 min read · 32 upvotes · 3 comments

## Summary

Supabase's Postgres Changes feature now supports three new capabilities: AND-combined multi-column filters (using comma-separated conditions), additional filter operators including like, ilike, is, match, imatch, and isdistinct (with not. prefix for inversion), and column selection so subscriptions only return specified fields. The primary key is always included in payloads. Column selection requires supabase-js 2.109.0+. Both improvements reduce billable message and egress costs. OR composition, array/JSON containment, full-text search, and range operators are not yet supported.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://supabase.com/blog/postgres-changes-filters-and-column-selection>

## Community discussion

Top comments from developers on daily.dev.

**@sbmagar13** · 0 upvotes

> Great! I'm already sold on the multi-column filters feature😃

**@trevorsuna** · 0 upvotes

> Column selection feels like the quiet win here. Sending only the fields a subscriber needs reduces egress, but it also makes realtime consumers easier to reason about. Keeping the primary key automatic is a sensible guardrail.

**@agustinbarrientos** · 0 upvotes

> I think the filter builder should be the default. Handwritten `status=eq.open,team=eq.billing` is one typo away from a silent subscription bug.

---

Tags: [#backend](https://daily.dev/tags/backend), [#postgresql](https://daily.dev/tags/postgresql), [#supabase](https://daily.dev/tags/supabase), [#websocket](https://daily.dev/tags/websocket)

[View this post on daily.dev](https://daily.dev/posts/postgres-changes-gets-and-filters-new-operators-and-column-selection-ejffdwnv1)