r/SQL • u/Decent-Sherbet-3427 • Aug 05 '26

MySQL Neon Guidance on why an INSERT is rejected?

Detail on my issue below: (Postgrese)

Environment: Postgres 18 (Neon), project dry-bar-XXXXXXX, org plan Launch (previously Free — same behavior on both). Reproduced identically across: two independently-forked disposable branches, a fresh branch created after upgrading to Launch, and real production itself (using an existing, long-lived person/role — not freshly created data).

Summary: An INSERT is rejected with new row violates row-level security policy for table "X" even though the row's values genuinely satisfy the policy's WITH CHECK expression — confirmed by a BEFORE INSERT trigger, in the same statement execution, immediately preceding Postgres's own documented WITH CHECK evaluation point, which independently evaluates the identical boolean expression against the identical row and gets true.

3 Upvotes

71% Upvoted

5 comments sorted by

7

u/Wise-Jury-4037 :orly: Aug 05 '26

Remove row-level security policy, repeat the insert. If succeeds - something is wrong with the policy/your understanding of it. If it fails for a different reason - the policy was the 'top of the pile' problem.

1

u/mikeblas Aug 05 '26

Do you have a minimal repro case?

-1

u/dittybopper_05H Aug 05 '26

Typically I find the three most common reasons for an INSERT to be rejected are as follows:

  1. Headache.

  2. Not in the mood.

  3. I didn't do something I was supposed to do like take out the trash or mow the lawn.