Forum: pg_bulkload 2.4.0 and 3.0alpha1 released
Posted by: Takahiro Itagaki It is 3 times or more faster than postgres' default loader because pg_bulkload uses less-overhead buffers, skipping WAL writing, and reuse existing indexes to fast index rebuild. pg_bulkload 2.4.0 and 3.0alpha1 support PostgreSQL 8.4, 8.3 and 8.2 on Windows and POSIX platforms. Also several new features are added. ------------------------------ pg_bulkload 2.4.0 ------------------------------ http://pgfoundry.org/frs/shownotes.php?release_id=1422 It supports PostgreSQL 8.4 and has several improvements for usability: parse error skipping, unique violation reports, and new command line options. [features] - Works on 8.4, 8.3 and 8.2. - Support skipping parse erros. At most MAX_ERR_CNT errors are ignored and continue loading. - Supports loading 2G or more rows at once. - Support build with pgxs (USE_PGXS). - Report conflicted keys on unique violations. - $PGDATA/pg_bulkload for load status file will be created automatically. - New command line options to pg_bulkload. + -i, --infile=INFILE : input file (accepts relative path) + -o="key=value" : additional options - Accepts CSV files with CR+LF for linebreaks. [bugfix] - Fix SIGBUS erros on non-x86 CPUs. - Fix loading to tables with functional btree index. - Avoid WAL writes during btree index build. ------------------------------ pg_bulkload 3.0 alpha 1 ------------------------------ http://pgfoundry.org/frs/shownotes.php?release_id=1423 This is a release for technology preview. It supports new features; unique violation error handling, parallel load, and load from remote data source. [features] - Resolve unique violation erros. The behavior is controlled by ON_DUPLICATE option. - Add parallel loader. If WRITER=PARALLEL is specified, input file reader and table writer are executed in dedicated backend processes. - Supports remote data source using COPY FROM protocol. Non-superusers can use remote loading.
|
Latest Newspg_bulkload 2.4.0 and 3.0alpha1 releasedTakahiro Itagaki - 2009-07-21 14:34 -
0 Comment Read More/Comment
|
Monitor Forum | 
