Re: PENDING_LIST_CLEANUP_SIZE - maximum size of GIN pending list Re: HEAD seems to generate larger WAL regarding GIN index

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jesper Krogh <jesper(at)krogh(dot)cc>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PENDING_LIST_CLEANUP_SIZE - maximum size of GIN pending list Re: HEAD seems to generate larger WAL regarding GIN index
Date: 2014-11-06 14:38:13
Message-ID: CAHGQGwEMK2VFx28oRhAPh3LvDNnCavNSe75hNtVoex=PptKFPw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 4, 2014 at 12:04 PM, Etsuro Fujita
<fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> IIUC, I think that min = 0 disables fast update, so ISTM that it'd be
> appropriate to set min to some positive value. And ISTM that the idea of
> using the min value of work_mem is not so bad.

OK. I changed the min value to 64kB.

> *** 356,361 **** CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] [ <replaceable
> class="parameter">name</
> --- 356,372 ----
> </listitem>
> </varlistentry>
> </variablelist>
> + <variablelist>
> + <varlistentry>
> + <term><literal>PENDING_LIST_CLEANUP_SIZE</></term>
>
> The above is still in uppercse.

Fixed.

Attached is the updated version of the patch. Thanks for the review!

Regards,

--
Fujii Masao

Attachment Content-Type Size
pending_list_cleanup_size_v6.patch text/x-patch 18.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2014-11-06 14:46:04 Re: Repeatable read and serializable transactions see data committed after tx start
Previous Message Greg Sabino Mullane 2014-11-06 14:24:29 Re: Repeatable read and serializable transactions see data committed after tx start