| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | iradu(at)unix-world(dot)org |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14297: ON CONFLICT fails |
| Date: | 2016-08-26 20:30:36 |
| Message-ID: | CAKFQuwaJkE-3fFGET0sQ0RDTYkeJhujJPCdgckGLyn7JdCgnRA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Aug 26, 2016 at 12:56 PM, <iradu(at)unix-world(dot)org> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 14297
> Logged by: Ilies Radu
> Email address: iradu(at)unix-world(dot)org
> PostgreSQL version: 9.5.4
> Operating system: Any
> Description:
> [...]
>
> Is this a bug or a not implemented feature (UPDATE ... ON CONFLICT)
>
>
Given the absence of an "ON CONFLICT" clause in the documentation its safe
to say its not implemented.
https://www.postgresql.org/docs/9.5/static/sql-update.html
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jason.christy | 2016-08-27 07:11:42 | BUG #14298: service upgrade not setting ports |
| Previous Message | Andrew Gierth | 2016-08-26 19:00:27 | Re: BUG #14296: weird check constraint clause in pg_constraint |