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

Re: strange behavior (corruption?) of large production database

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: strange behavior (corruption?) of large production database
Date: 2005-12-03 00:47:15
Message-ID: 10244.1133570835@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Joe Conway <mail(at)joeconway(dot)com> writes:
> Since this database has many large, but static tables (i.e. new data is 
> loaded each day, but the tables are partitioned into year-month tables), 
> I'm thinking we can run VACUUM FREEZE on the whole database once, and 
> then run VACUUM FREEZE periodically on just the tables that have had 
> rows added since the last time -- is that correct?

That would work for the user tables, but the lesson to draw from this is
not to forget about the system catalogs ...

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Joe ConwayDate: 2005-12-03 00:51:37
Subject: Re: strange behavior (corruption?) of large production
Previous:From: Tom LaneDate: 2005-12-03 00:43:24
Subject: Re: Optimizer oddness, possibly compounded in 8.1

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