| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Erin Munro <emunro(at)ll(dot)mit(dot)edu> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: WAL disk space |
| Date: | 2002-12-09 16:47:08 |
| Message-ID: | 8513.1039452428@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Erin Munro <emunro(at)ll(dot)mit(dot)edu> writes:
> An empty database cluster takes up 20 MB, 16 of which
> are dedicated to a WAL file. This seems to be a lot
> for a small or low-traffic database. Is there any way
> to reduce the size of this WAL file, besides reverting
> to version 7.0 (where WAL isn't used)?
Reduce XLogSegSize in src/include/access/xlog.h. Recompile,
re-initdb (or at least do pg_resetxlog), put up with more frequent
checkpoints.
With sufficiently low write activity this might be worthwhile, but
I find it hard to think of any recently-manufactured hardware wherein
16MB of disk space is worth agonizing over.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brian Fujito | 2002-12-09 17:45:33 | "dumpProcLangs(): handler procedure for language plpgsql not found" on 7.0.3 |
| Previous Message | Stephan Szabo | 2002-12-09 16:33:10 | Re: WAL disk space |