Re: Renaming a DB

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Mendola Gaetano <mendola(at)bigfoot(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Renaming a DB
Date: 2003-07-21 04:09:27
Message-ID: 19811.1058760567@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom, why was a VACUUM FULL required?

I doubt that it was; a VACUUM would have sufficed to fix the tuple
commit bits. What I forgot to recommend was a CHECKPOINT to make
sure the fixed pages got dumped to disk. (Until they're written
out to the kernel, a new backend would still see the old pages
when it's doing the GetRawDatabaseInfo cruft.)

I think a VAC FULL would have flushed dirty pages, but a plain VACUUM
wouldn't, so VAC FULL is a second way of getting the result.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Bruce Momjian 2003-07-21 04:20:00 Re: Renaming a DB
Previous Message Bruce Momjian 2003-07-21 03:58:40 Re: Renaming a DB