| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org>, mboscia <mboscia(at)cymer(dot)com> |
| Subject: | Re: strange behavior (corruption?) of large production |
| Date: | 2005-12-03 00:51:37 |
| Message-ID: | 4390EC19.2090006@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> 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 ...
>
Right, I was just thinking about that too. Important safety tip :-)
Thanks again!
Joe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Charles F. I. Savage | 2005-12-03 00:54:32 | Building Windows Server Extensions Using VC++ 2005 |
| Previous Message | Tom Lane | 2005-12-03 00:47:15 | Re: strange behavior (corruption?) of large production database |