aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorThomas Munro <tmunro@postgresql.org>2019-02-18 09:53:26 +1300
committerThomas Munro <tmunro@postgresql.org>2019-02-18 09:58:29 +1300
commit0b55aaacec313c309e21f63d9ff5733c3f8ab813 (patch)
treea231f56cca57dfc3b1cb5bc708dbb218c636608a /src/backend/executor/nodeModifyTable.c
parentbc6d7eb689a2d083df981dfd10c65d1a9d32ca64 (diff)
downloadpostgresql-0b55aaacec313c309e21f63d9ff5733c3f8ab813.tar.gz
postgresql-0b55aaacec313c309e21f63d9ff5733c3f8ab813.zip
Fix race in dsm_unpin_segment() when handles are reused.
Teach dsm_unpin_segment() to skip segments that are in the process of being destroyed by another backend, when searching for a handle. Such a segment cannot possibly be the one we are looking for, even if its handle matches. Another slot might hold a recently created segment that has the same handle value by coincidence, and we need to keep searching for that one. The bug caused rare "cannot unpin a segment that is not pinned" errors on 10 and 11. Similar to commit 6c0fb941 for dsm_attach(). Back-patch to 10, where dsm_unpin_segment() landed. Author: Thomas Munro Reported-by: Justin Pryzby Tested-by: Justin Pryzby (along with other recent DSA/DSM fixes) Discussion: https://postgr.es/m/20190216023854.GF30291@telsasoft.com
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions