Re: BUG #14397: Updatable VIEW doesn't work with ON CONFLICT from PgPreparedStatement

Hi David and Peter,

Yes, I did this cross posting to ​http://stackoverflow.com/
questions/40260920/updatable-view-doesnt-work-with-on-
conflict-in-postgres-9-5​ So it's not a bug but a limitation which is quite
logical but is not reflected in documentation. According to Postgres bug
reporting guideline
<https://www.postgresql.org/docs/current/static/bug-reporting.html> "If it
is not clear from the documentation whether you can do something or not,
please report that too; it is a bug in the documentation" should I create a
separate bug to improve documentation or can we use this one?

Thanks,
Grygoriy

On Mon, Oct 31, 2016 at 6:09 PM, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

>
>
> On Wed, Oct 26, 2016 at 2:24 AM, <grygoriy(dot)gonchar(at)kreditech(dot)com> wrote:
>
>> The following bug has been logged on the website:
>>
>> Bug reference: 14397
>> Logged by: Grygoriy Gonchar
>> Email address: grygoriy(dot)gonchar(at)kreditech(dot)com
>> PostgreSQL version: 9.5.4
>> Operating system: x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 4.8.2
>> Description:
>>
>> ​[...]​
>>
>>
>> An exception or error caused a run to abort: ERROR: ON CONFLICT is not
>> supported on table "test" used as a catalog table
>>
>
> ​Any chance you cross-posted this to Stack Overflow? A Google search on
> "used as a catalog table" turns up a post from 5 days ago that is awfully
> similar.
>
> ​http://stackoverflow.com/questions/40260920/updatable-view-
> doesnt-work-with-on-conflict-in-postgres-9-5​
>
> ​The conclusion there is that we seem to have a RLS interaction failure.
> I suspect this isn't a code bug but a known, if under-documented,
> limitation though others more versed with these two features need to chime
> in.
>
> David J.
>