| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | Derek Hans <derek(dot)hans(at)gmail(dot)com> |
| Cc: | Sergei Kornilov <sk(at)zsrv(dot)org>, "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 15:12:25 |
| Message-ID: | CA+HiwqF3gma5HfCJb4_cOk0_+LEpVc57EHdBfz_EKt+Nu0hNYg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
On Mon, Mar 4, 2019 at 10:58 PM Derek Hans <derek(dot)hans(at)gmail(dot)com> wrote:
>
> 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.
Perhaps, it would make sense to make a note related to this in the
partitioning chapter where various limitations are listed and link to
it from the v11 release notes.
I've attached a patch. It applies to the PG 11 stable branch, but the
ddl.sgml part of the patch should also be applied to master.
Thanks,
Amit
| Attachment | Content-Type | Size |
|---|---|---|
| document-update-row-movement-limitation.patch | application/octet-stream | 1.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dirkjan Ochtman | 2019-03-04 15:47:05 | Re: BUG #15666: Seemingly incorrect error reporting/logging for violation of non-null constraint |
| Previous Message | Jeremy Finzel | 2019-03-04 14:28:36 | Re: Segmentation Fault in logical decoding get/peek API |