Received: from sss.pgh.pa.us (sss.pgh.pa.us [216.151.103.158]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f4BNUDA86046 for ; Fri, 11 May 2001 19:30:13 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f4BNU5R07779; Fri, 11 May 2001 19:30:05 -0400 (EDT) To: webb sprague cc: pgsql-general@postgresql.org Subject: Re: WAL logs eating my diskspace!! In-reply-to: <0105111540060A.08603@lappi.o1.com> References: <000601c0d202$203b2b10$2001a8c0@blockhead> <3AF83B71.1C8DDDFA@mindark.com> <01051110103601.08603@lappi.o1.com> <0105111540060A.08603@lappi.o1.com> Comments: In-reply-to webb sprague message dated "Fri, 11 May 2001 15:40:06 -0400" Date: Fri, 11 May 2001 19:30:05 -0400 Message-ID: <7776.989623805@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200105/546 X-Sequence-Number: 9399 webb sprague writes: > Is there a way to flush them more often? Reduce the time interval between WAL checkpoints. (But don't overdo it.) Perhaps every three or so minutes, rather than five? > Otherwise, they can fill up the > disk space and crash the postmaster. I am doing bulk copies, but the logs > hang around for up to 20 minutes after the copy is finished. Another possibility is to issue a manual CHECKPOINT command as soon as you've finished a bulk copy. regards, tom lane