Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 0D4B11997F5C for ; Tue, 12 Jun 2012 04:50:35 -0300 (ADT) Received: from mail-pz0-f46.google.com ([209.85.210.46]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SeLs0-0001zy-FA for pgsql-admin@postgresql.org; Tue, 12 Jun 2012 07:50:34 +0000 Received: by dady13 with SMTP id y13so6512733dad.19 for ; Tue, 12 Jun 2012 00:50:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=5qfLmjcFBvjpaSoZv90bkm0i+FTyNw1u0frsoVLx1o0=; b=S3SZp1KKHaeUJVHNNCqdGDWOu7esThmd0WjX8iq3GoWoHsf67I8vflAyf6GZvoUnm5 XwXa+vVcJEivkjsXNApqsmnuR1fZp6NblZBgnjXOydZxKx7h43flmCbSg2B+wVYGV+Eo 01YH6seUrEhufRI7tfTPIyjCu1sf65Z8ZZxHDDawBMeIyjMv0YopBzHWurbcCCH4kbpH 4TZ4OUI9sJNj1W9gfQg83QiNraCZc1CnqVH7MNWiK/I24KICHMBA/Ad40H4sicr2QgwY OGoS7EyVY+/ty1QONJIgGVnCcZ1NhVMK771cfY8zWasyCStI3kvA5sJfoBBbQm9x+qzy IJXA== Received: by 10.68.228.2 with SMTP id se2mr37004108pbc.109.1339487417434; Tue, 12 Jun 2012 00:50:17 -0700 (PDT) Received: from [192.168.1.10] ([116.226.54.24]) by mx.google.com with ESMTPS id nh8sm1151727pbc.60.2012.06.12.00.50.14 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Jun 2012 00:50:16 -0700 (PDT) Message-ID: <4FD6F4B3.8050509@gmail.com> Date: Tue, 12 Jun 2012 15:50:11 +0800 From: Rural Hunter User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120604 Thunderbird/13.0 MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Why auto vacuum almost running all the time on one toast table? Content-Type: text/plain; charset=GB18030; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.4 (--) X-Archive-Number: 201206/57 X-Sequence-Number: 39648 v9.1.3 on Ubuntu 10.04 server. I have one table which has frequent insert and weekly deletion, no update. Recently, I found the auto vacuum on the toast table of it almost running all the time. each run took around 1 hour. I don't think there are so many inerts so that it reaches the auto vacuum criteria(20%? changes). And there is no such frequent auto vacuum on the main table. The last auto vacuum of the main table is on 3rd Jun. what might cause this behavior? # grep pg_toast_16922 postgresql-2012-06-12_000000.log 2012-06-12 01:22:56 CST [@] CONTEXT: automatic vacuum of table "oodb.pg_toast.pg_toast_16922" 2012-06-12 04:27:49 CST [@] CONTEXT: automatic vacuum of table "oodb.pg_toast.pg_toast_16922" 2012-06-12 06:58:02 CST [@] CONTEXT: automatic vacuum of table "oodb.pg_toast.pg_toast_16922" 2012-06-12 09:27:38 CST [@] CONTEXT: automatic vacuum of table "oodb.pg_toast.pg_toast_16922" 2012-06-12 12:17:33 CST [@] CONTEXT: automatic vacuum of table "oodb.pg_toast.pg_toast_16922" 2012-06-12 15:05:31 CST [@] CONTEXT: automatic vacuum of table "oodb.pg_toast.pg_toast_16922"