Adrian von Bidder <avbid...@fortytwo.ch> writes:
> With our test dump, the db (after import) is ca. 300M on disk, ca. half in
> WAL files (pg_xlog.) If I could mostly get rid of the WAL (keep it to a
> bare minimum and run pg without fsync, something like that), the remaining
> 160 to 180M would be ok.
checkpoint_segments is the main tunable determining the amount of WAL
space. Lowering it will increase the amount of write activity, but
for a ramdisk I don't think you care.
Depending on your usage patterns, it might be worth making autovacuum
more aggressive to ensure that table bloat stays under control.
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
