diff options
| author | Melanie Plageman <melanieplageman@gmail.com> | 2025-04-03 18:22:37 -0400 |
|---|---|---|
| committer | Melanie Plageman <melanieplageman@gmail.com> | 2025-04-03 18:22:37 -0400 |
| commit | 54a3615f15b9b2e1433bc47cfb150317885d7c1f (patch) | |
| tree | d6d75e266f08e0ef754be90364076e5d7de62e5e /src/backend/access/gist/gistvacuum.c | |
| parent | dbd437e670b88ca67f6b2477e853412a0e82a8cc (diff) | |
| download | postgresql-54a3615f15b9b2e1433bc47cfb150317885d7c1f.tar.gz postgresql-54a3615f15b9b2e1433bc47cfb150317885d7c1f.zip | |
Remove misleading read stream asserts in a few users
Several read stream users asserted that the read stream was exhausted
after looping on that very condition. It was pointed out in an a
review of an as-of-yet uncommitted read stream user [1] that this was
confusing and could lead the reader to think there was a possibility of
some kind of race condition. Remove these asserts.
[1] https://postgr.es/m/F9ACE8D0-B807-4A17-B6BD-87EF0717983D%40yesql.se
Diffstat (limited to 'src/backend/access/gist/gistvacuum.c')
| -rw-r--r-- | src/backend/access/gist/gistvacuum.c | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/src/backend/access/gist/gistvacuum.c b/src/backend/access/gist/gistvacuum.c index ce9d78d78d6..6a359c98c60 100644 --- a/src/backend/access/gist/gistvacuum.c +++ b/src/backend/access/gist/gistvacuum.c @@ -254,8 +254,6 @@ gistvacuumscan(IndexVacuumInfo *info, IndexBulkDeleteResult *stats, gistvacuumpage(&vstate, buf); } - Assert(read_stream_next_buffer(stream, NULL) == InvalidBuffer); - /* * We have to reset the read stream to use it again. After returning * InvalidBuffer, the read stream API won't invoke our callback again |