How BareSQL Audit Finds Every Column a PostgreSQL Login Can Read

Mon, 26 Oct 2026 00:00:00 +0000

PostgreSQL keeps the answer to “who can read this column?” in many places. Grants sit in access lists on tables and on single columns. Role memberships nest, and since PostgreSQL 16 each one says separately whether its rights are inherited and whether SET ROLE is allowed. Views read their tables with their owner’s rights unless they say otherwise, row security policies filter what a table hands out, and default privileges hand out tables that don’t exist yet.

How BareSQL Portable Finds SQL That Answers Differently on Four Engines

Mon, 26 Oct 2026 00:00:00 +0000

Most SQL that fails on another engine fails loudly, with a syntax error on the first run. The expensive kind runs everywhere and answers differently. On the sample shop’s products, SUM(stock) / COUNT(*) is 3 on SQLite and PostgreSQL and 3.3333 on MySQL. ORDER BY last_order puts the customers who never ordered first on three engines and last on PostgreSQL. A search with LIKE finds Ann on SQLite and misses her on PostgreSQL, and '1' = 1 is false on SQLite and true on the other three. None of these raise an error.

Explainers on BareSQL.com

How BareSQL Audit Finds Every Column a PostgreSQL Login Can Read

How BareSQL Portable Finds SQL That Answers Differently on Four Engines