Version: Postgres 7.1.2 A product we are developing requires frequent loading of a large number of rows into a table. We are using the "copy file" command, but with WAL we are effectively doubling the amount of disk writing we are doing. After the rows are loaded we do a "create index". Is there a way to turn off WAL or otherwise speeding up the table loading process? Would db_restore be faster? The rows are loaded in sorted order. Does this impact index creation negatively or positively? We are currently working with test data but we estimate production data to be 6 - 9 billion rows. Is anyone else running with these volumes? Simon ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
