Re: autovacuum worker running amok - and me too ;)

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: wambacher <wnordmann(at)gmx(dot)de>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: autovacuum worker running amok - and me too ;)
Date: 2015-04-07 23:44:55
Message-ID: 55246BF7.4040207@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 3/9/15 3:56 AM, wambacher wrote:
> Hi paul
>
> just found my system (24 GB Mem, 72 GB Swap) running nearly at it's limits:
>
> The current vaccum is using 66.7 GB (sixty-six dot seven) GB of memory and
> my System is nearly down.
>
> I'm sorry, but that must be an bug. Remember: It's the Analyze of an
> GIN-Index that is making that problems. Various tables - same Problem.
>
> Regards
> walter
>
> <http://postgresql.nabble.com/file/n5841074/top.png>
> duríng the last 10 Minutes vaccum took one more GB, now it's using 67.5 if
> mem.
>
> should i ask at the dev-list? Open a ticket?

Sorry for the late reply.

Yes, that sounds like a bug in the GIN code. Please post to pgsql-bugs
or hit http://www.postgresql.org/support/submitbug/
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jim Nasby 2015-04-08 00:16:22 Re: Asynchronous replication in postgresql
Previous Message Jim Nasby 2015-04-07 23:17:27 Re: Problems with casting