Bruce Momjian <[EMAIL PROTECTED]> writes:
> Added to TODO based on this discussion:
> o To better utilize resources, restore data, primary keys, and
> indexes for a single table before restoring the next table
That idea seems quite misguided, and certainly was not anywhere in the
prior discussion. If you add an ordering constraint as strong as that,
you'll mostly just eliminate chances for parallelism. Also, the
following para describes something completely different:
> 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.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your Subscription:
http://mail.postgresql.org/mj/mj_wwwusr?domain=postgresql.org&extra=pgsql-hackers
