Skip site navigation (1) Skip section navigation (2)

Re: count on transaction ID

From: ddgs <gsmaths(at)gmail(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: count on transaction ID
Date: 2012-03-12 16:34:37
Message-ID: 1331570077139-5558345.post@n5.nabble.com (view raw or flat)
Thread:
Lists: pgsql-performance
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.

In response to

Responses

pgsql-performance by date

Next:From: Scott MarloweDate: 2012-03-12 16:37:54
Subject: Re: Tuning wizard
Previous:From: Tomas VondraDate: 2012-03-12 16:10:28
Subject: Re: Advice on Controller card for SAS disks

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group