Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: exclusion@gmail.com, pgsql-bugs@lists.postgresql.org
Date: 2023-10-02T02:56:35Z
Lists: pgsql-bugs
On Sat, Sep 30, 2023 at 08:39:37PM -0400, Tom Lane wrote: > I think it's OK as is. What we are comparing in the modified logic > is whether index columns at the same column positions are expressions or > not, and that's not a matter for mapping. Once we've verified that > the current column is a non-expression in both indexes, then it's > appropriate to use the attmap to see whether the columns correspond. FWIW, I was thinking about a case like that with 2 index attributes: info1->attr[0] = 0, info1->attr[1] = 1 info2->attr[0] = 1, info2->attr[1] = 0 With a mapping from info2 to info1 like that: attmap[0] = 1, attmap[1] = 0. The code before 9f71e10d6 would have accessed an incorrect pointer. The new code would return false, which would not be correct if the expressions stored in ii_Expressions for info1/attr0 and info2/attr1 match? -- Michael
Commits
-
Fix checking of index expressions in CompareIndexInfo().
- 3caedf246123 11.22 landed
- d6425987ba76 12.17 landed
- 9f71e10d65fa 17.0 landed
- 9d6d8d7049ea 14.10 landed
- 83ba050f92fa 13.13 landed
- 59371f1aeb9a 15.5 landed
- 12402b93117b 16.1 landed