Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id 8C3592E004F for ; Mon, 12 May 2008 05:20:14 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 36419-10 for ; Mon, 12 May 2008 05:19:57 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.173]) by developer.postgresql.org (Postfix) with ESMTP id 50F702E004E for ; Mon, 12 May 2008 05:20:01 -0300 (ADT) Received: by wf-out-1314.google.com with SMTP id 25so2169676wfc.28 for ; Mon, 12 May 2008 01:20:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=6sIqjo7pJBW/XHf+glFGRuLgWBTa862wUVGDJUHPbpE=; b=nZSh2luswB+08MYbrKbj8Hr5eHtyxqxNv04/RMwhtxSGvyroFNCf87KazGH4OQvqfLHlSr3SXltnMQJyhA7tyUgQVU8/Vcux8Ju/dZf5sLdDJdgyRx6MZQT3OhR9cATwA3IkLvWbgUjYdSz9pZCqmoGCe4H9nw4VAPwmTx/bJPQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=xCh2ZGs1gz4XXMOfSyR0VIHDiFKlYCj01gRlBdcxaPal7nOPW2M4gKxLdQ0OYe5mb+oyoEjfZqKf89rvZ9ogJYqrMv4BrRv7+z3YqeFpAHz3TW8aG47BF65wlt7F7HLTMfkphzMX3I+G9TKxvwL6cT8y8clox9tdci3B8rjrqtg= Received: by 10.143.44.17 with SMTP id w17mr3142108wfj.242.1210580399469; Mon, 12 May 2008 01:19:59 -0700 (PDT) Received: by 10.142.88.10 with HTTP; Mon, 12 May 2008 01:19:59 -0700 (PDT) Message-ID: <8d01be800805120119l7fb4fc29m8755f6c087797143@mail.gmail.com> Date: Mon, 12 May 2008 10:19:59 +0200 From: "James Farrugia" To: "Tino Schwarze" Subject: Re: Orphan TOAST object Cc: pgsql-admin@postgresql.org In-Reply-To: <20080512073546.GA30621@easy2.in-chemnitz.de> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_143_31305302.1210580399460" References: <8d01be800805110946r792efacdp3dbe02829b6da7a9@mail.gmail.com> <20553.1210525788@sss.pgh.pa.us> <8d01be800805111017w6910acdapaf66f0b56908d36e@mail.gmail.com> <20763.1210526763@sss.pgh.pa.us> <8d01be800805120025u3a49fa39rc7033a2480b4982f@mail.gmail.com> <20080512073546.GA30621@easy2.in-chemnitz.de> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200805/88 X-Sequence-Number: 29172 ------=_Part_143_31305302.1210580399460 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Tino, That was what we suspected and in fact didn't want to run any unnecessary risks. Thanks again. James. On 5/12/08, Tino Schwarze wrote: > > Hi James, > > On Mon, May 12, 2008 at 09:25:34AM +0200, James Farrugia wrote: > > > First of all thanks for the immediate replies! > > Was actually waiting for the right moment to upgrade to 8.3 but > migrating a > > live 1Tb database is a bit daunting especially if you have never done it > > before (as in my case). If I'm not mistaken i can upgrade to the latest > > minor version without having to dump and restore so I'll do that. > > You need to check the release notes of the particulra minor release you > are upgrading to. Some minor releases also require a dump/restore cycle > because of bugfixes. You're lucky: 8.2.7 doesn't require dump/restore in > your case, the release notes say: > "A dump/restore is not required for those running 8.2.X" > > > One last thing...can we run into data-loss problems with successfully > > vacuumed tables even if there is one unvacuumed database object; what > would > > have happened if I ignored to vacuum that rogue pg_toast (which was the > only > > unvacuumed object within the entire database)? > > At a certain point, the server would have switched to "emergency mode" > and wouldn't have accepted any commands any more. See the description > here: > > http://www.postgresql.org/docs/8.2/static/routine-vacuuming.html#VACUUM-FOR-WRAPAROUND > > HTH, > > Tino. > > -- > "What we resist, persists." (Zen saying) > > www.craniosacralzentrum.de > www.forteego.de > > -- > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin > ------=_Part_143_31305302.1210580399460 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Hi Tino,
 
That was what we suspected and in fact didn't want to run any unnecessary risks.  Thanks again.
 
James.

 
On 5/12/08, Tino Schwarze <postgresql@tisc.de> wrote:
Hi James,

On Mon, May 12, 2008 at 09:25:34AM +0200, James Farrugia wrote:

> First of all thanks for the immediate replies!
> Was actually waiting for the right moment to upgrade to 8.3 but migrating a
> live 1Tb database is a bit daunting especially if you have never done it
> before (as in my case).  If I'm not mistaken i can upgrade to the latest
> minor version without having to dump and restore so I'll do that.

You need to check the release notes of the particulra minor release you
are upgrading to. Some minor releases also require a dump/restore cycle
because of bugfixes. You're lucky: 8.2.7 doesn't require dump/restore in
your case, the release notes say:
"A dump/restore is not required for those running 8.2.X"

> One last thing...can we run into data-loss problems with successfully
> vacuumed tables even if there is one unvacuumed database object; what would
> have happened if I ignored to vacuum that rogue pg_toast (which was the only
> unvacuumed object within the entire database)?

At a certain point, the server would have switched to "emergency mode"
and wouldn't have accepted any commands any more. See the description
here:
http://www.postgresql.org/docs/8.2/static/routine-vacuuming.html#VACUUM-FOR-WRAPAROUND

HTH,

Tino.

--
"What we resist, persists." (Zen saying)

www.craniosacralzentrum.de
www.forteego.de

--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

------=_Part_143_31305302.1210580399460--