Problem

When using pgschema plan against a database with RLS policies that reference functions in the public schema, pgschema reports changes even when the policies are semantically identical. This creates a perpetual diff that reappears after every apply.

Reproduction

1. Create a function and policy:

CREATE FUNCTION public.auth_uid() RETURNS uuid AS $$
  SELECT gen_random_uuid();
$$ LANGUAGE sql;

CREATE TABLE public.users (
  id uuid PRIMARY KEY,
  org_id uuid NOT NULL
);

ALTER TABLE public.users ENABLE ROW LEVEL SECURITY;

CREATE POLICY "select_own" ON public.users FOR SELECT
  USING (org_id IN (SELECT auth_uid()));

2. Create a schema file with the same policy (using unqualified auth_uid()):

CREATE POLICY "select_own" ON public.users FOR SELECT
  USING (org_id IN (SELECT auth_uid()));

3. Run pgschema plan --schema public - it shows a modification even though nothing changed.

4. Run pgschema apply - applies the "change".

5. Run pgschema plan again - the same modification reappears.

Root Cause

There's a mismatch between how pgschema normalizes expressions and how PostgreSQL stores them:

When pgschema compares desired vs actual:

• Desired (after pgschema normalization): public.auth_uid()
• Actual (from pg_get_expr): auth_uid()
• Result: perpetual diff

Relation to Issue #218

This is similar to #218 ("Schema qualifiers stripped from column default expressions"), but in the opposite direction and for a different object type:

The #218 fix added normalization logic to treat ::public.status and ::status as equivalent during comparison. A similar normalization for function calls in policy expressions would resolve this issue.

Expected Behavior

pgschema plan should show no changes when the policy expressions are semantically equivalent, regardless of whether the function reference is schema-qualified.

Environment

• pgschema version: 1.5.1
• PostgreSQL version: 15.x (via Supabase local)
• Target schema: public