pgsql: For bulk write operations (eg COPY IN), use a ring buffer of 16MB - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: For bulk write operations (eg COPY IN), use a ring buffer of 16MB
Date
Msg-id 20090622200428.8FF0D75331E@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
For bulk write operations (eg COPY IN), use a ring buffer of 16MB instead
of the 256KB limit originally enforced by a patch committed 2008-11-06.
Per recent test results, the smaller size resulted in an undesirable decrease
in bulk data loading speed, due to COPY processing frequently getting blocked
for WAL flushing.  This area might need more tweaking later, but this setting
seems to be good enough for 8.4.

Modified Files:
--------------
    pgsql/src/backend/storage/buffer:
        README (r1.16 -> r1.17)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/buffer/README?r1=1.16&r2=1.17)
        freelist.c (r1.66 -> r1.67)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/buffer/freelist.c?r1=1.66&r2=1.67)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Make to_timestamp and friends skip leading spaces before an
Next
From: devrim@pgfoundry.org (User Devrim)
Date:
Subject: press - pr: Turkish translation of release.translate.txt for 8.4.