From: ddgs <gsmaths@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: count on transaction ID
Date: Mon, 12 Mar 2012 09:34:37 -0700 (PDT)
Message-ID: <1331570077139-5558345.post@n5.nabble.com> (raw)
In-Reply-To: <4F5DD88F020000250004610B@gw.wicourts.gov>
References: <1331307029713-5550894.post@n5.nabble.com>
<4F5DC49D02000025000460F6@gw.wicourts.gov>
<1331567213547-5558198.post@n5.nabble.com>
<4F5DD88F020000250004610B@gw.wicourts.gov>
Is it a good starting point to the basic reason of doing vacuum?
from the manual,
"PostgreSQL's VACUUM command must be run on a regular basis for several
reasons:
To recover disk space occupied by updated or deleted rows.
To update data statistics used by the PostgreSQL query planner.
To protect against loss of very old data due to transaction ID wraparound.
"
It seems that only transaction ID wraparound can cause system failure in
loading-in new data.
For the dead rows problem, it just a matter of space; the data statistics is
just relate to the query performance.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/count-on-transaction-ID-tp5550894p5558345.html
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: gsmaths@gmail.com
Subject: Re: count on transaction ID
In-Reply-To: <1331570077139-5558345.post@n5.nabble.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox