From: | momjian(at)postgresql(dot)org (Bruce Momjian) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Remove: < < o To better utilize resources, restore data, |
Date: | 2008-03-04 02:48:22 |
Message-ID: | 20080304024822.8B67C754108@cvs.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Log Message:
-----------
Remove:
<
< o To better utilize resources, restore data, primary keys, and
< indexes for a single table before restoring the next table
<
< Hopefully this will allow the CPU-I/O load to be more uniform
< for simultaneous restores. The idea is to start data restores
< for several objects, and once the first object is done, to move
< on to its primary keys and indexes. Over time, simultaneous
< data loads and index builds will be running.
Modified Files:
--------------
pgsql/doc:
TODO (r1.2253 -> r1.2254)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/TODO?r1=1.2253&r2=1.2254)
pgsql/doc/src/FAQ:
TODO.html (r1.762 -> r1.763)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html?r1=1.762&r2=1.763)
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2008-03-04 03:17:18 | pgsql: Show example of ts_headline() using a configuration name. |
Previous Message | Bruce Momjian | 2008-03-04 01:38:37 | pgsql: Add URL for: o Allow pg_restore to utilize multiple CPUs |