-
- Downloads
Rename various "freeze multixact" variables
It seems to make more sense to use "cutoff multixact" terminology throughout the backend code; "freeze" is associated with replacing of an Xid with FrozenTransactionId, which is not what we do for MultiXactIds. Andres Freund Some adjustments by Álvaro Herrera
Showing
- src/backend/access/heap/heapam.c 2 additions, 2 deletionssrc/backend/access/heap/heapam.c
- src/backend/access/heap/rewriteheap.c 6 additions, 6 deletionssrc/backend/access/heap/rewriteheap.c
- src/backend/access/transam/multixact.c 1 addition, 1 deletionsrc/backend/access/transam/multixact.c
- src/backend/commands/cluster.c 16 additions, 15 deletionssrc/backend/commands/cluster.c
- src/backend/commands/dbcommands.c 1 addition, 1 deletionsrc/backend/commands/dbcommands.c
- src/backend/commands/vacuum.c 22 additions, 22 deletionssrc/backend/commands/vacuum.c
- src/backend/commands/vacuumlazy.c 6 additions, 6 deletionssrc/backend/commands/vacuumlazy.c
- src/backend/postmaster/autovacuum.c 4 additions, 5 deletionssrc/backend/postmaster/autovacuum.c
- src/include/access/rewriteheap.h 1 addition, 1 deletionsrc/include/access/rewriteheap.h
- src/include/commands/cluster.h 1 addition, 1 deletionsrc/include/commands/cluster.h
- src/include/commands/vacuum.h 1 addition, 1 deletionsrc/include/commands/vacuum.h
Loading
Please register or sign in to comment