| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Subject: | Re: unique, partitioned index fails to distinguish index key from INCLUDEd columns |
| Date: | 2019-01-15 04:21:24 |
| Message-ID: | 201901150421.mlogf4cts5tj@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-Jan-14, Justin Pryzby wrote:
> On Mon, Jan 14, 2019 at 07:31:07PM -0300, Alvaro Herrera wrote:
> > Doh. Fix pushed. Commit 8224de4f42cc should have changed one
> > appearance of ii_NumIndexAttrs to ii_NumIndexKeyAttrs, but because of
> > the nature of concurrent development, nobody noticed.
>
> I figured as much - I thought to test this while trying to fall asleep,
> without knowing they were developed in parallel.
:-)
> Should backpatch to v11 ?
> 0ad41cf537ea5f076273fcffa4c83a184bd9910f
Yep, already done (src/tools/git_changelog in master):
Author: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Branch: master [0ad41cf53] 2019-01-14 19:28:10 -0300
Branch: REL_11_STABLE [74aa7e046] 2019-01-14 19:25:19 -0300
Fix unique INCLUDE indexes on partitioned tables
We were considering the INCLUDE columns as part of the key, allowing
unicity-violating rows to be inserted in different partitions.
Concurrent development conflict in eb7ed3f30634 and 8224de4f42cc.
Reported-by: Justin Pryzby
Discussion: https://postgr.es/m/20190109065109.GA4285@telsasoft.com
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2019-01-15 04:29:23 | Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 |
| Previous Message | Haribabu Kommi | 2019-01-15 04:08:41 | current_logfiles not following group access and instead follows log_file_mode permissions |