Received: from localhost (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id 5E33B62DBEB
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Mon,  5 Jan 2009 15:18:15 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 44511-03 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Mon,  5 Jan 2009 15:18:12 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from hermes.vectorsf.com (firewall.vectorsf.com [62.82.80.62])
	by mail.postgresql.org (Postfix) with ESMTP id 43EA862DBE0
	for <pgsql-admin@postgresql.org>; Mon,  5 Jan 2009 15:18:12 -0400 (AST)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by hermes.vectorsf.com (Postfix) with ESMTP id 4BA1A11C01B6;
	Mon,  5 Jan 2009 20:18:05 +0100 (CET)
X-Virus-Scanned: amavisd-new at hermes.vectorsf.com
Received: from hermes.vectorsf.com ([127.0.0.1])
	by localhost (hermes.vectorsf.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id fNtrRXRGEme1; Mon,  5 Jan 2009 20:18:01 +0100 (CET)
Received: from hermes.vectorsf.com (hermes.vectorsf.com [10.70.4.30])
	by hermes.vectorsf.com (Postfix) with ESMTP id 2130711C00CE;
	Mon,  5 Jan 2009 20:18:01 +0100 (CET)
From: =?iso-8859-1?Q?I=F1igo_Martinez_Lasala?= <imartinez@vectorsf.com>
To: "'Ygor Degani'" <ygordegani@gmail.com>,
	<pgsql-admin@postgresql.org>
References: <4bb7c9f80901050517l3743891ax93ad672a07054b14@mail.gmail.com>
Subject: Re: error vacuum full
Date: Mon, 5 Jan 2009 20:18:01 +0100 (CET)
Message-ID: <E2676F6898A74FFEA529DFA1F74CAF51@DEIMOS>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_05E8_01C96F72.AC686F10"
X-Mailer: Microsoft Office Outlook 11
X-Mailer: Zimbra 5.0.11_GA_2695.RHEL4_64
	(ZimbraConnectorForOutlook/5.0.2767.10)
In-Reply-To: <4bb7c9f80901050517l3743891ax93ad672a07054b14@mail.gmail.com>
Thread-Index: AclvSRrR3C8cIqJXTmKa0LNPHcisKwAIPMgA
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Originating-IP: [88.3.105.16]
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: 200901/17
X-Sequence-Number: 31064

This is a multi-part message in MIME format.

------=_NextPart_000_05E8_01C96F72.AC686F10
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

What about your mantainance_mem parameter in postgresql.conf? If it is
very high, are you sure do you have free memory enough?
I had a similar problem two weeks ago due to this issue and I had to low
effective_cache_size in order to get memory enough for vacuum process.


  _____  

De: Ygor Degani [mailto:ygordegani@gmail.com] 
Enviado el: lunes, 05 de enero de 2009 14:18
Para: pgsql-admin@postgresql.org
Asunto: [ADMIN] error vacuum full


I use postgres-8.3.5. My database has 168 GB in size. Whenever i try to do
vacuum full happens the following error:
 
WARNING:  terminating connection because of crash of another server
process
DETAIL:  The postmaster has commanded this server process to roll back the
current transaction and exit, because another server process exited
abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and
repeat your command.
vacuumdb: vacuuming of database "acotel_brazil_vas" failed: server closed
the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.

If i have autovacuum enabled, Do i need to do vacuum full?


Regards,
-- 
Ygor Degani



------=_NextPart_000_05E8_01C96F72.AC686F10
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16788" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D828041619-05012009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>What about your mantainance_mem parameter in=20
postgresql.conf? If it is very high, are you sure do you have free =
memory=20
enough?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D828041619-05012009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I had a similar problem two weeks ago due to =
this issue and=20
I had to low effective_cache_size in order to get memory enough for =
vacuum=20
process.</FONT></SPAN></DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Des dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>De:</B> Ygor Degani =
[mailto:ygordegani@gmail.com]=20
  <BR><B>Enviado el:</B> lunes, 05 de enero de 2009 =
14:18<BR><B>Para:</B>=20
  pgsql-admin@postgresql.org<BR><B>Asunto:</B> [ADMIN] error vacuum=20
  full<BR></FONT><BR></DIV>
  <DIV></DIV>I use postgres-8.3.5. My database has 168 GB in size. =
Whenever i=20
  try to do vacuum full happens the following error:<BR>&nbsp;<BR=20
  clear=3Dall>WARNING:&nbsp; terminating connection because of crash of =
another=20
  server process<BR>DETAIL:&nbsp; The postmaster has commanded this =
server=20
  process to roll back the current transaction and exit, because another =
server=20
  process exited abnormally and possibly corrupted shared =
memory.<BR>HINT:&nbsp;=20
  In a moment you should be able to reconnect to the database and repeat =
your=20
  command.<BR>vacuumdb: vacuuming of database "acotel_brazil_vas" =
failed: server=20
  closed the connection=20
  unexpectedly<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This =
probably means=20
  the server terminated =
abnormally<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  before or while processing the request.<BR><BR>If i have autovacuum =
enabled,=20
  Do i need to do vacuum full?<BR><BR><BR>Regards,<BR>-- <BR>Ygor=20
Degani<BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_05E8_01C96F72.AC686F10--