Received: from maia.hub.org (maia-5.hub.org [200.46.204.29])
	by mail.postgresql.org (Postfix) with ESMTP id 996511336FA7
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Sat,  9 Apr 2011 11:31:55 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024)
	with ESMTP id 43146-04 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Sat,  9 Apr 2011 14:31:47 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from tamriel.snowman.net (tamriel.snowman.net [72.66.115.51])
	by mail.postgresql.org (Postfix) with ESMTP id 17351133616B
	for <pgsql-admin@postgresql.org>; Sat,  9 Apr 2011 11:31:44 -0300 (ADT)
Received: by tamriel.snowman.net (Postfix, from userid 1000)
	id 38F252298B; Sat,  9 Apr 2011 10:31:45 -0400 (EDT)
Date: Sat, 9 Apr 2011 10:31:45 -0400
From: Stephen Frost <sfrost@snowman.net>
To: Erwin Brandstetter <brsaweda@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: 20110408pg upgrade fix: How do I know if I am being
	affected before errors occur
Message-ID: <20110409143145.GM4548@tamriel.snowman.net>
References: 
 <9cd57df6-665f-41b0-899e-efe070e2e50e@f30g2000yqa.googlegroups.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="x38akuY2VS0PywU3"
Content-Disposition: inline
In-Reply-To: 
 <9cd57df6-665f-41b0-899e-efe070e2e50e@f30g2000yqa.googlegroups.com>
X-Editor: Vim http://www.vim.org/
X-Info: http://www.snowman.net
X-Operating-System: Linux/2.6.32-5-amd64 (x86_64)
X-Uptime: 10:30:12 up 65 days, 23:00, 37 users,  load average: 0.22, 0.06,
 0.02
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201104/72
X-Sequence-Number: 37253


--x38akuY2VS0PywU3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Erwin,

* Erwin Brandstetter (brsaweda@gmail.com) wrote:
>  - Can applying the proposed fix break anything if the db wasn't
> affected to begin with?

Running a database-wide 'vacuum freeze;' will either succeed (and all
will be well), or it'll generate the errors in the message (in which
case you'll need to restore the CLOG files, as at the wiki page, and
then re-run the 'vacuum freeze;').

	Thanks,

		Stephen

--x38akuY2VS0PywU3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk2gbdEACgkQrzgMPqB3kii3kACdG4UldofkGdEposkcrEOBOUB6
E3kAoJY/9pyClwZmwrcLQb9rrugtuIhP
=eHk7
-----END PGP SIGNATURE-----

--x38akuY2VS0PywU3--