PostgreSQL TODO List

====================

Current maintainer:Bruce Momjian (bruce@momjian.us)

Last updated:Mon Mar 320:38:32 EST 2008

Last updated:Mon Mar 321:48:18 EST 2008

The most recent version of this document can be viewed at

http://www.postgresql.org/docs/faqs.TODO.html.

-Fc format has the necessary dependency information.

http://archives.postgresql.org/pgsql-hackers/2008-02/msg00963.php

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.

o To better utilize resources, allow pg_restore to check foreign

keys simultaneously, where possible

o Allow pg_restore to create all indexes of a table

<bodybgcolor="#FFFFFF"text="#000000"link="#FF0000"vlink="#A00000"alink="#0000FF">

<h1><aname="section_1">PostgreSQL TODO List</a></h1>

<p>Current maintainer: Bruce Momjian (<ahref="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>

Last updated: Mon Mar 320:38:32 EST 2008

Last updated: Mon Mar 321:48:18 EST 2008

<p>The most recent version of this document can be viewed at<br/>

<ahref="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.

simultaneous operations should be performed. Only pg_dump's

-Fc format has the necessary dependency information.

<ahref="http://archives.postgresql.org/pgsql-hackers/2008-02/msg00963.php">http://archives.postgresql.org/pgsql-hackers/2008-02/msg00963.php</a>

</li><li>To better utilize resources, restore data, primary keys, and

indexes for a single table before restoring the next table

<p> 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.

</li><li>To better utilize resources, allow pg_restore to check foreign

keys simultaneously, where possible