diff options
| author | Michael Paquier <michael@paquier.xyz> | 2023-07-14 11:15:34 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2023-07-14 11:15:34 +0900 |
| commit | a5ea825f958c2de9fadb825cbf16bf9b1360f0df (patch) | |
| tree | f4ea65dfea689698015e2baf90c258f0706eda25 /src/backend/parser/parse_clause.c | |
| parent | 38ea6aa90e615fc91c138fc1efbc981ef3b434f8 (diff) | |
| download | postgresql-a5ea825f958c2de9fadb825cbf16bf9b1360f0df.tar.gz postgresql-a5ea825f958c2de9fadb825cbf16bf9b1360f0df.zip | |
Add indisreplident to fields refreshed by RelationReloadIndexInfo()
RelationReloadIndexInfo() is a fast-path used for index reloads in the
relation cache, and it has always forgotten about updating
indisreplident, which is something that would happen after an index is
selected for a replica identity. This can lead to incorrect cache
information provided when executing a command in a transaction context
that updates indisreplident.
None of the code paths currently on HEAD that need to check upon
pg_index.indisreplident fetch its value from the relation cache, always
relying on a fresh copy on the syscache. Unfortunately, this may not be
the case of out-of-core code, that could see out-of-date value.
Author: Shruthi Gowda
Reviewed-by: Robert Haas, Dilip Kumar, Michael Paquier
Discussion: https://postgr.es/m/CAASxf_PBcxax0wW-3gErUyftZ0XrCs3Lrpuhq4-Z3Fak1DoW7Q@mail.gmail.com
Backpatch-through: 11
Diffstat (limited to 'src/backend/parser/parse_clause.c')
0 files changed, 0 insertions, 0 deletions