aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistproc.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2025-04-02 11:13:01 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2025-04-02 11:13:01 -0400
commitdd34cbfce296007165e896ce19b5177a9d1b87e1 (patch)
treeba8b2b2ba0fe1dab114cb6d402c7219cbd8fd4e9 /src/backend/access/gist/gistproc.c
parentebbdaf1fd59d3bad4bb0aee346ad6f8a225549d1 (diff)
downloadpostgresql-dd34cbfce296007165e896ce19b5177a9d1b87e1.tar.gz
postgresql-dd34cbfce296007165e896ce19b5177a9d1b87e1.zip
Need to do CommandCounterIncrement after StoreAttrMissingVal.
Without this, an additional change to the same pg_attribute row within the same command will fail. This is possible at least with ALTER TABLE ADD COLUMN on a multiple-inheritance-pathway structure. (Another potential hazard is that immediately-following operations might not see the missingval.) Introduced by 95f650674, which split the former coding that used a single pg_attribute update to change both atthasdef and atthasmissing/attmissingval into two updates, but missed that this should entail two CommandCounterIncrements as well. Like that fix, back-patch through v13. Reported-by: Alexander Lakhin <exclusion@gmail.com> Author: Tender Wang <tndrwang@gmail.com> Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us> Discussion: https://postgr.es/m/025a3ffa-5eff-4a88-97fb-8f583b015965@gmail.com Backpatch-through: 13
Diffstat (limited to 'src/backend/access/gist/gistproc.c')
0 files changed, 0 insertions, 0 deletions