Re: proposal: CREATE DATABASE vs. (partial) CHECKPOINT
От | Jim Nasby |
---|---|
Тема | Re: proposal: CREATE DATABASE vs. (partial) CHECKPOINT |
Дата | |
Msg-id | 5452C45A.1060607@BlueTreble.com обсуждение исходный текст |
Ответ на | Re: proposal: CREATE DATABASE vs. (partial) CHECKPOINT (Heikki Linnakangas <hlinnakangas@vmware.com>) |
Ответы |
Re: proposal: CREATE DATABASE vs. (partial) CHECKPOINT
|
Список | pgsql-hackers |
On 10/30/14, 2:13 PM, Heikki Linnakangas wrote: > On 10/30/2014 08:56 PM, Andres Freund wrote: >> I actually think we should *always* use the new code and not >> add a separate wal_level=minimal branch. Maintaining this twice just >> isn't worth the effort. minimal is used *far* less these days. > > I wouldn't go that far. Doing the wal_level=minimal optimization should be pretty straightforward. Note that it would beimplemented more like CREATE INDEX et al with wal_level=minimal, not the way CREATE DATABASE currently works. It wouldnot involve any extra checkpoints. +1 At my previous job, we used createdb -T copy_from_production new_dev_database, because that was far faster than re-loadingthe raw SQL dump all the time. It'd be a shame to have that need to write the copied data 2x. IIRC that databasewas around 20MB. -- Jim Nasby, Data Architect, Blue Treble Consulting Data in Trouble? Get it in Treble! http://BlueTreble.com
В списке pgsql-hackers по дате отправления: