Vacuum Vs Vacuum Full

From: Robert Shaw <redsmurfau(at)msn(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Subject: Vacuum Vs Vacuum Full
Date: 2008-08-05 06:04:00
Message-ID: BLU141-W10E024CC64094BA938A2B3DD7B0@phx.gbl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


Hi,

I've been trying to get to the bottom of the differences between a vacuum and a vacuum full, it seems to me that the difference is that a vacuum full also recovers disk space(and locks things making it less than useful on production servers). But I believe that both will fix the transaction ID(example message below).

"WARNING: database "mydb" must be vacuumed within 177009986 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "mydb"."Which is reason I ask the question, is full vacuum backup useful for anything other than reclaiming disk space.

On a side note, we doubled our page slots, but they ran out much faster(of course) than we thought, is there a good sql statement that can tell you what your current transaction ID is?

Thanks in advance.

Cheers,
Rob

_________________________________________________________________
Are you paid what you're worth? Find out: SEEK Salary Centre
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau%2Fcareer%2Dresources%2Fsalary%2Dcentre%2F%3Ftracking%3Dsk%3Ahet%3Asc%3Anine%3A0%3Ahot%3Atext&_t=764565661&_r=OCT07_endtext_salary&_m=EXT

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Sim Zacks 2008-08-05 07:12:26 mailing list/newsgroup disconnect
Previous Message Sim Zacks 2008-08-05 05:37:25 Re: bytea encode performance issues