| From: | Derek Hans <derek(dot)hans(at)gmail(dot)com> |
|---|---|
| To: | Sergei Kornilov <sk(at)zsrv(dot)org> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15662: Row update in foreign partition does not move row based on partition key |
| Date: | 2019-03-04 13:57:48 |
| Message-ID: | CAGrP7a2vkbuu5RLd4yC4TP7nwpTbqLt5pfpS5a7-decy7yxq3w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Thanks. That's a substantial limitation.
I looked pretty hard through the various pieces of documentation and
tutorials and saw no mention. The v11 release notes don't mention it
either. Might be worth adding to the docs in more places and more
prominently.
On Fri, Mar 1, 2019 at 2:54 PM Sergei Kornilov <sk(at)zsrv(dot)org> wrote:
> Hello
>
> This is known limitation and documented in the notes section of the UPDATE
> reference page:
>
> > "Currently, rows cannot be moved from a partition that is a foreign
> table to some other partition, but they can be moved into a foreign table
> if the foreign data wrapper supports it."
>
> https://www.postgresql.org/docs/11/sql-update.html
>
> regards, Sergei
>
--
*Derek*
+1 (415) 754-0519 | derek(dot)hans(at)gmail(dot)com | Skype: derek.hans
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-03-04 14:27:43 | Re: BUG #15666: Seemingly incorrect error reporting/logging for violation of non-null constraint |
| Previous Message | PG Bug reporting form | 2019-03-04 09:55:31 | BUG #15666: Seemingly incorrect error reporting/logging for violation of non-null constraint |