-
- Downloads
Change WAL-logging scheme for multixacts to be more like regular
transaction IDs, rather than like subtrans; in particular, the information now survives a database restart. Per previous discussion, this is essential for PITR log shipping and for 2PC.
Showing
- doc/src/sgml/ref/pg_resetxlog.sgml 21 additions, 7 deletionsdoc/src/sgml/ref/pg_resetxlog.sgml
- src/backend/access/heap/heapam.c 17 additions, 7 deletionssrc/backend/access/heap/heapam.c
- src/backend/access/transam/multixact.c 426 additions, 195 deletionssrc/backend/access/transam/multixact.c
- src/backend/access/transam/rmgr.c 3 additions, 2 deletionssrc/backend/access/transam/rmgr.c
- src/backend/access/transam/xlog.c 18 additions, 43 deletionssrc/backend/access/transam/xlog.c
- src/bin/pg_controldata/pg_controldata.c 2 additions, 1 deletionsrc/bin/pg_controldata/pg_controldata.c
- src/bin/pg_resetxlog/pg_resetxlog.c 25 additions, 3 deletionssrc/bin/pg_resetxlog/pg_resetxlog.c
- src/include/access/htup.h 3 additions, 1 deletionsrc/include/access/htup.h
- src/include/access/multixact.h 33 additions, 4 deletionssrc/include/access/multixact.h
- src/include/access/xlog.h 1 addition, 2 deletionssrc/include/access/xlog.h
- src/include/c.h 3 additions, 1 deletionsrc/include/c.h
- src/include/catalog/pg_control.h 3 additions, 3 deletionssrc/include/catalog/pg_control.h
Loading
Please register or sign in to comment