diff options
| author | Thomas Munro <tmunro@postgresql.org> | 2019-02-18 09:53:26 +1300 |
|---|---|---|
| committer | Thomas Munro <tmunro@postgresql.org> | 2019-02-18 09:59:27 +1300 |
| commit | 1d93d180454f9da74677dd0498f5408efe6b603d (patch) | |
| tree | 291787be2f32fb4e947db144e7b00fa881dff51a /src/backend/access/gist/gistvacuum.c | |
| parent | 7f39f0344129706979174ba530f8cc21b7d9f4a3 (diff) | |
| download | postgresql-1d93d180454f9da74677dd0498f5408efe6b603d.tar.gz postgresql-1d93d180454f9da74677dd0498f5408efe6b603d.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/access/gist/gistvacuum.c')
0 files changed, 0 insertions, 0 deletions