← Back to branch summary

~ubuntu-branches/ubuntu/natty/postgresql-8.4/natty-security

« back to all changes in this revision

Viewing changes to src/backend/storage/buffer/README

  • Committer: Bazaar Package Importer
  • Author(s): Martin Pitt
  • Date: 2009-07-11 16:59:35 UTC
  • mfrom: (5.1.1 karmic)
  • Revision ID: james.westby@ubuntu.com-20090711165935-jfwin6gfrxf0gfsi
Tags: 8.4.0-2
http://bugs.debian.org/536139
* debian/libpq-dev.install: Ship catalog/genbki.h. (Closes: #536139)
* debian/rules: Drop --enable-cassert for final release.

Show diffs side-by-side

added added

removed removed

Lines of Context:
src/backend/storage/buffer/README
1
 
$PostgreSQL: pgsql/src/backend/storage/buffer/README,v 1.16 2009/02/18 15:58:41 heikki Exp $
 
1
$PostgreSQL: pgsql/src/backend/storage/buffer/README,v 1.17 2009/06/22 20:04:28 tgl Exp $
2
2
 
3
3
Notes About Shared Buffer Access Rules
4
4
======================================
237
237
 
238
238
Bulk writes work similarly to VACUUM.  Currently this applies only to
239
239
COPY IN and CREATE TABLE AS SELECT.  (Might it be interesting to make
240
 
seqscan UPDATE and DELETE use the bulkwrite strategy?)
 
240
seqscan UPDATE and DELETE use the bulkwrite strategy?)  For bulk writes
 
241
we use a ring size of 16MB (but not more than 1/8th of shared_buffers).
 
242
Smaller sizes have been shown to result in the COPY blocking too often
 
243
for WAL flushes.  While it's okay for a background vacuum to be slowed by
 
244
doing its own WAL flushing, we'd prefer that COPY not be subject to that,
 
245
so we let it use up a bit more of the buffer arena.
241
246
 
242
247
 
243
248
Background Writer's Processing