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

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: For bulk write operations (eg COPY IN), use a ring buffer of 16MB
Date: 2009-06-22 20:04:28
Message-ID: 20090622200428.8FF0D75331E@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

Browse pgsql-committers by date

  From Date Subject
Next Message User Devrim 2009-06-22 20:55:53 press - pr: Turkish translation of release.translate.txt for 8.4.
Previous Message Tom Lane 2009-06-22 17:54:30 pgsql: Make to_timestamp and friends skip leading spaces before an