Minor code rationalization: FlushRelationBuffers just returns void,
rather than an error code, and does elog(ERROR) not elog(WARNING) when it detects a problem. All callers were simply elog(ERROR)'ing on failure return anyway, and I find it hard to envision a caller that would not, so we may as well simplify the callers and produce the more useful error message directly.
Showing
- src/backend/access/nbtree/nbtree.c 2 additions, 6 deletionssrc/backend/access/nbtree/nbtree.c
- src/backend/catalog/heap.c 2 additions, 5 deletionssrc/backend/catalog/heap.c
- src/backend/catalog/index.c 2 additions, 5 deletionssrc/backend/catalog/index.c
- src/backend/commands/cluster.c 3 additions, 8 deletionssrc/backend/commands/cluster.c
- src/backend/commands/vacuum.c 4 additions, 10 deletionssrc/backend/commands/vacuum.c
- src/backend/commands/vacuumlazy.c 2 additions, 4 deletionssrc/backend/commands/vacuumlazy.c
- src/backend/storage/buffer/bufmgr.c 7 additions, 24 deletionssrc/backend/storage/buffer/bufmgr.c
- src/include/storage/bufmgr.h 2 additions, 2 deletionssrc/include/storage/bufmgr.h
Loading
Please register or sign in to comment