Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints
Bruce Momjian <bruce@momjian.us>
On Mon, Feb 14, 2022 at 12:27:10PM -0500, Robert Haas wrote: > On Mon, Feb 14, 2022 at 11:26 AM Dilip Kumar <dilipbalaut@gmail.com> wrote: > > So do we have consensus to use (STRATEGY = LOG/CHECKPOINT or do we > > think that keeping it bool i.e. Is LOG_COPIED_BLOCKS a better option? > > Once we have consensus on this I will make this change and > > documentation as well along with the other changes suggested by > > Robert. > > I think we have consensus on STRATEGY. I'm not sure if we have > consensus on what the option values should be. If we had an option to > use fs-based cloning, that would also need to issue a checkpoint, > which makes me think that CHECKPOINT is not the best name. I think if we want LOG, it has tob e WAL_LOG instead of just LOG. Was there discussion that the user _has_ to specify and option instead of using a default? That doesn't seem good. -- Bruce Momjian <bruce@momjian.us> https://momjian.us EDB https://enterprisedb.com If only the physical world exists, free will is an illusion.
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