... - Mailing list pgsql-general

From News Subsystem
Subject ...
Date
Msg-id 201304091121.r39BLq45032652@news.hub.org
Whole thread Raw
List pgsql-general
        Tue, 09 Apr 2013 04:21:51 -0700 (PDT)
 09 Apr 2013 04:21:50 -0700 (PDT)
X-Newsgroups: pgsql.general
Date: Tue, 9 Apr 2013 04:21:50 -0700 (PDT)
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=210.143.35.31;
 posting-account=GbL1LQoAAAA52LT6cIjZnkdtjTyQZ5G0
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <47408590-a31c-4541-a2e4-1da06bb7c64b@googlegroups.com>
Subject: Vacuuming time of template1 db
From: hdsarma@gmail.com
Injection-Date: Tue, 09 Apr 2013 11:21:50 +0000
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
To: pgsql-general@postgresql.org

We do routine vacuuming of all db's every hour that is postgres, template1 =
and one user database.The user db is used quite heavily, but to our surpris=
e it take least vacuuming time, generally template1 takes most of the time =
followed by postgres and then the user db, template1 db is never used in ou=
r system is there any reason why it takes most time for vacuuming.


pgsql-general by date:

Previous
From: News Subsystem
Date:
Subject: ...
Next
From: ROBERT KLAUS
Date:
Subject: Are partitions getting pruned?