Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints
Tom Lane <tgl@sss.pgh.pa.us>
Robert Haas <robertmhaas@gmail.com> writes: > WARNING: problem in alloc set PortalContext: req size > alloc size > for chunk 0x7f99508911f0 in block 0x7f9950890800 > WARNING: problem in alloc set PortalContext: bad size 0 for chunk > 0x7f99508911f0 in block 0x7f9950890800 > WARNING: problem in alloc set PortalContext: bad single-chunk > 0x7f9950891208 in block 0x7f9950890800 > WARNING: problem in alloc set PortalContext: found inconsistent > memory block 0x7f9950890800 > WARNING: problem in alloc set PortalContext: req size > alloc size > for chunk 0x7f99508911f0 in block 0x7f9950890800 > WARNING: problem in alloc set PortalContext: bad size 0 for chunk > 0x7f99508911f0 in block 0x7f9950890800 > WARNING: problem in alloc set PortalContext: bad single-chunk > 0x7f9950891208 in block 0x7f9950890800 > WARNING: problem in alloc set PortalContext: found inconsistent > memory block 0x7f9950890800 This looks like nothing so much as the fallout from something scribbling past the end of an allocated palloc chunk, or perhaps writing on already-freed space. Perhaps running the test case under valgrind would help to finger the culprit. regards, tom lane
Commits
-
When using the WAL-logged CREATE DATABASE strategy, bulk extend.
- 3e63e8462f31 16.0 landed
- 576bb0fc9342 15.0 landed
-
Avoid using a fake relcache entry to own an SmgrRelation.
- 1b94f8f232f6 15.0 landed
- 76733b399c49 16.0 landed
-
Fix data-corruption hazard in WAL-logged CREATE DATABASE.
- 692df425b688 16.0 landed
- 811203d4aff5 15.0 landed
-
initdb: When running CREATE DATABASE, use STRATEGY = WAL_COPY.
- ad43a413c4f7 15.0 landed
-
Simplify a needlessly-complicated regular expression.
- c6863b858291 15.0 landed
-
In 020_createdb.pl, change order of command-line arguments.
- 3d067c53b26d 15.0 landed
-
Add new block-by-block strategy for CREATE DATABASE.
- 9c08aea6a309 15.0 landed
-
Fix replay of create database records on standby
- 49d9cfc68bf4 15.0 cited
-
Refactor code for reading and writing relation map files.
- 39f0c4bd670c 15.0 landed
-
Replace RelationOpenSmgr() with RelationGetSmgr().
- f10f0ae420ee 15.0 cited
-
Refactor the fsync queue for wider use.
- 3eb77eba5a51 12.0 cited