On Fri, Feb 11, 2022 at 4:08 PM Alvaro Herrera <alvhe...@alvh.no-ip.org> wrote: > It seems you're thinking deciding what to do based on an option that > gets a boolean argument. But what about making the argument be an enum? > For example > > CREATE DATABASE ... WITH (STRATEGY = LOG); -- default if option is > omitted > CREATE DATABASE ... WITH (STRATEGY = CHECKPOINT); > > So the user has to think about it in terms of some strategy to choose, > rather than enabling or disabling some flag with nontrivial > implications.
I don't like those particular strategy names very much, but in general I think that could be a way to go, too. I somewhat hope we never end up with THREE strategies for creating a new database, but now that I think about it, we might. Somebody might want to use a fancy FS primitive that clones a directory at the FS level, or something. -- Robert Haas EDB: http://www.enterprisedb.com
