| From: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, 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 |
| Date: | 2019-03-06 04:04:28 |
| Message-ID: | 5C7F46CC.6010801@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
(2019/03/06 11:34), Amit Langote wrote:
> 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.)
I'm not sure it's a good idea to make changes to the release notes like
that, because 1) that would make the release notes verbose, and 2) it
might end up doing the same thing to items that have some limitations in
the existing/future release notes (eg, FOR EACH ROW triggers on
partitioned tables added to V11 has the limitation listed on the
limitation section, so the same link would be needed.), for consistency.
Best regards,
Etsuro Fujita
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2019-03-06 04:18:00 | Re: Update does not move row across foreign partitions in v11 |
| Previous Message | David Rowley | 2019-03-06 03:47:47 | Re: Update does not move row across foreign partitions in v11 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro HORIGUCHI | 2019-03-06 04:05:02 | Re: Protect syscache from bloating with negative cache entries |
| Previous Message | Robbie Harwood | 2019-03-06 03:55:23 | Re: [PATCH v20] GSSAPI encryption support |