| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | grygoriy(dot)gonchar(at)kreditech(dot)com |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14397: Updatable VIEW doesn't work with ON CONFLICT from PgPreparedStatement |
| Date: | 2016-10-31 17:09:58 |
| Message-ID: | CAKFQuwYP+0aUnMXxWeDfkCo1KHeT+mZF9Lq3Tf4P6ccF7BgWeQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Grygoriy Gonchar | 2016-10-31 17:27:12 | Re: BUG #14397: Updatable VIEW doesn't work with ON CONFLICT from PgPreparedStatement |
| Previous Message | Peter Geoghegan | 2016-10-31 16:55:38 | Re: BUG #14397: Updatable VIEW doesn't work with ON CONFLICT from PgPreparedStatement |