Received: from brasileiro.net (slxwy.dorms.usu.edu [129.123.236.160]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g15Gskl04904 for ; Tue, 5 Feb 2002 11:54:46 -0500 (EST) (envelope-from roberto@brasileiro.net) Received: from roberto by brasileiro.net with local (Exim 3.34 #1 (Debian)) id 16Y8rv-0007gP-00 for ; Tue, 05 Feb 2002 09:54:55 -0700 Date: Tue, 5 Feb 2002 09:54:55 -0700 From: Roberto Mello To: pgsql-sql@postgresql.org Subject: WAL filling up disk Message-ID: <20020205165455.GA29166@cc.usu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.27i X-Archive-Number: 200202/55 X-Sequence-Number: 6486 Hi all, There was a question on the postgresql-br list the other day that I couldn't answer and was curious about it. This guy has is evaluating PG 7.1(.1?) and has a 1 million records table. He then does a "update tablefoo set somefield = 123" and WAL eventually causes his 4 Gb disk to fill up and never complete the transaction. According to him, there are over 250 16Mb files under pg_xlog (I understand 16 Mb is the default segment file size for WAL). Can anyone give me more details as to why this happens and the possible configurations that should be changed? Thanks in advance. -Roberto -- +----| http://fslc.usu.edu/ USU Free Software & GNU/Linux Club |------+ Roberto Mello - Computer Science, USU - http://www.brasileiro.net/ http://www.sdl.usu.edu/ - Space Dynamics Lab, Developer * * * <- Tribbles . . . <- Tribbles after a haircut