From: | Peter Geoghegan <pg(at)heroku(dot)com> |
---|---|
To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net> |
Subject: | Re: Row security violation error is misleading |
Date: | 2015-04-07 20:11:09 |
Message-ID: | CAM3SWZTJhNbFCS9t7u+mS1ob_Jrwp1v9VTnGb4UBh8osgj14sg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Apr 7, 2015 at 5:11 AM, Craig Ringer <craig(at)2ndquadrant(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2015-04-07 20:19:07 | Re: pg_restore -t should match views, matviews, and foreign tables |
Previous Message | Peter Eisentraut | 2015-04-07 19:41:57 | Re: Auditing extension for PostgreSQL (Take 2) |