Postgres Pro
Downloads
Home   >   mailing lists

Thread: error vacuum full

error vacuum full

From
"Ygor Degani"
Date:
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

Re: error vacuum full

From
Alvaro Herrera
Date:
Ygor Degani escribió:
> 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

If you have server processes crashing, you should investigate that.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

Re: error vacuum full

From
"Scott Marlowe"
Date:
On Mon, Jan 5, 2009 at 6:17 AM, Ygor Degani <ygordegani@gmail.com> wrote:
> 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?

You have two problems.  One is you're running vacuum full regularly,
which you shouldn't need, and which can cause bloated indexes.  Normal
autovacuum should handle your database fine unless you're deleting a
huge part of a table over and over.

As to why it's crashing, that's another story.  Anything in the system
logs about the oom killer kicking in?  Have you got work_mem set to
something huge?  maintenance work mem really huge?  shared_buffers,
etc?  What have you changed from stock in postgresql.conf?

Re: error vacuum full

From
Iñigo Martinez Lasala
Date:
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