Re: FSM versus GIN pending list bloat

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: FSM versus GIN pending list bloat
Date: 2015-08-04 15:17:28
Message-ID: CANP8+j+q_YjatQ9cjcMaqLuKLERHH87qtGOwvhvPqvXH8sRUOQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 4 August 2015 at 15:18, Andres Freund <andres(at)anarazel(dot)de> wrote:

> On 2015-08-04 14:59:11 +0100, Simon Riggs wrote:
> > On 4 August 2015 at 14:55, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
> >
> > > On 08/04/2015 04:35 PM, Simon Riggs wrote:
> > >
> > >> This and the OP seem like 9.5 open items to me.
> > >>
> > >
> > > Why? This is nothing new in 9.5.
> >
> >
> > gin_pending_list_limit is new in 9.5
> >
> > We're in Alpha, so if something has been added and isn't very usable, we
> > should change it while we can.
>
> The only thing that variable does is change what the pending size limit
> is determined by. Previously it was work_mem, now it's
> gin_pending_list_limit. Imo that has pretty much nothing to do with not
> registering pages as free.
>

We've made a change to the way GIN fast update works and that needs to be
an effective change, not one that immediately triggers a secondary
annoyance for the user. I've asked some questions; they may turn into
actions, or not, but they are open items.

--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2015-08-04 15:19:29 Re: Autonomous Transaction is back
Previous Message Heikki Linnakangas 2015-08-04 15:03:33 Re: Sharing aggregate states between different aggregate functions