Re: GIN fast insert

From: Teodor Sigaev <teodor(at)sigaev(dot)ru>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: GIN fast insert
Date: 2009-02-11 18:47:14
Message-ID: 49931D32.5090101@sigaev.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas wrote:
>> I believe that user could get GIN's error about work_mem only intentionally:
>> - turn off autovacuum
> Meanwhile, in the other thread, we're having a discussion about people
> wanting to do exactly this on a database-wide basis during peak load
> hours...
>> - decrease work_mem for at least ten times
>> - execute query
> Why would the new work_mem need to be 10x smaller than the old work mem?

That is is way to get GIN's error emitted. Work_mem should be decreased
to catch a chance to get lossy tidbitmap.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gianni Ciolli 2009-02-11 18:48:02 Re: HotStandby vs. flatfile updates
Previous Message Tom Lane 2009-02-11 18:39:10 Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog,