From: "Carlos Sotto Maior \(SIM\)" <csotto@sistemassim.com.br>
To: <pgsql-admin@postgresql.org>
References: 
 <9cd57df6-665f-41b0-899e-efe070e2e50e@f30g2000yqa.googlegroups.com>
	<20110409143145.GM4548@tamriel.snowman.net>
In-Reply-To: <20110409143145.GM4548@tamriel.snowman.net>
Subject: RES: 20110408pg upgrade fix: How do I know if I am being affected
	before errors occur
Date: Thu, 14 Apr 2011 16:07:57 -0300
Message-ID: <00bc01cbfad7$4e67f6e0$eb37e4a0$@sistemassim.com.br>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQLe0mm1cPvm+EOHw1h8pkD6upg9sADdkJw7kjEZB/A=
Content-Language: pt-br

Hi,=20

I just noticed this thread today.=20
I am running 9.0.3.  I Read the 20110408 upgrade fix announcement, =
checked
pg_clog/ and noticed that it show only a single 0000 file.

I understand I may be hit by the mentioned problem.

Yes, I do have all tar archives available, but since my Database is
relatively small I can afford dumping / recreating and restoring this =
night
which is great.

My questions are:
Having a single 0000 in the pg_clog directory is indicative that my =
database
has been hit ?
If I run a database wise 'vacuum freeze' and all goes well does it means =
I
do not have to take any action?
Dumping and recreating the data base would be my best option to get rid =
of
this potential  problem. Correct ?

Thanks,

Carlos Sotto Maior
+55 11 8244-7899
csotto@sistemassim.com.br

Sistemas Sim Servi=E7os e Tecnologia Ltda.
+55 11 5041-3086
Rua Tenente Gomes Ribeiro, 78
Vila Clementino (Pr=F3ximo ao Metro Santa Cruz)
S=E3o Paulo - SP=20
04038-040

-----Mensagem original-----
De: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] Em nome de Stephen Frost
Enviada em: s=E1bado, 9 de abril de 2011 11:32
Para: Erwin Brandstetter
Cc: pgsql-admin@postgresql.org
Assunto: Re: [ADMIN] 20110408pg upgrade fix: How do I know if I am being
affected before errors occur

Erwin,

* Erwin Brandstetter (brsaweda@gmail.com) wrote:
>  - Can applying the proposed fix break anything if the db wasn't=20
> 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