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

From Fujii Masao
Subject Re: PENDING_LIST_CLEANUP_SIZE - maximum size of GIN pending list Re: HEAD seems to generate larger WAL regarding GIN index
Date
Msg-id CAHGQGwEMK2VFx28oRhAPh3LvDNnCavNSe75hNtVoex=PptKFPw@mail.gmail.com
Whole thread Raw
In response to Re: PENDING_LIST_CLEANUP_SIZE - maximum size of GIN pending list Re: HEAD seems to generate larger WAL regarding GIN index  (Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>)
Responses Re: PENDING_LIST_CLEANUP_SIZE - maximum size of GIN pending list Re: HEAD seems to generate larger WAL regarding GIN index  (Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>)
List pgsql-hackers
On Tue, Nov 4, 2014 at 12:04 PM, Etsuro Fujita
<fujita.etsuro@lab.ntt.co.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

pgsql-hackers by date:

Previous
From: "Greg Sabino Mullane"
Date:
Subject: Re: Repeatable read and serializable transactions see data committed after tx start
Next
From: Kevin Grittner
Date:
Subject: Re: Repeatable read and serializable transactions see data committed after tx start