Re: Row security violation error is misleading - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Row security violation error is misleading
Date
Msg-id CAM3SWZTJhNbFCS9t7u+mS1ob_Jrwp1v9VTnGb4UBh8osgj14sg@mail.gmail.com
Whole thread Raw
In response to Row security violation error is misleading  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
On Tue, Apr 7, 2015 at 5:11 AM, Craig Ringer <craig@2ndquadrant.com> wrote:
> postgres=> INSERT INTO clients (account_name, account_manager) VALUES
> ('peters', 'peter'), ('johannas', 'johanna');
> ERROR:  44000: new row violates WITH CHECK OPTION for "clients"
> DETAIL:  Failing row contains (7, johannas, johanna).
> LOCATION:  ExecWithCheckOptions, execMain.c:1683
>
>
> ... yet "clients" is a table, not a view, and cannot have a WITH CHECK
> OPTION clause.
>
> There is no reference to the policy being violated or to the fact that it's
> row security involved.


FWIW, I also think that this is very confusing.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Auditing extension for PostgreSQL (Take 2)
Next
From: Peter Eisentraut
Date:
Subject: Re: pg_restore -t should match views, matviews, and foreign tables