|From:||Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>|
|To:||David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>|
|Cc:||PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Derek Hans <derek(dot)hans(at)gmail(dot)com>|
|Subject:||Re: Update does not move row across foreign partitions in v11|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On 2019/03/06 11:29, David Rowley wrote:
> On Wed, 6 Mar 2019 at 15:26, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>>> I've tried to put all this right again in the attached. However, I was
>>> a bit unsure of what "but they can be moved into a foreign table if
>>> the foreign data wrapper supports it." is referring to. Copying Robert
>>> and Etsuro as this was all added in 3d956d9562aa. Hopefully, they can
>>> confirm what is meant by this.
>> Did you miss my reply on that thread?
> Yes. I wasn't aware that there were two threads for this.
Ah, indeed. In the documentation fix patch I'd posted, I also made
changes to release-11.sgml to link to the limitations section. (I'm
attaching it here for your reference.)
|Next Message||Etsuro Fujita||2019-03-06 03:29:24||Re: Update does not move row across foreign partitions in v11|
|Previous Message||David Rowley||2019-03-06 02:29:44||Re: Update does not move row across foreign partitions in v11|
|Next Message||Michael Paquier||2019-03-06 02:36:40||Re: Online verification of checksums|
|Previous Message||Andres Freund||2019-03-06 02:34:03||Re: Pluggable Storage - Andres's take|