Re: Reduce pinning in btree indexes - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Reduce pinning in btree indexes
Date
Msg-id CA+U5nMKHNAb99jvHwdmM4feheLZTB4TBAV4YN6r4jwAuv8u9Qw@mail.gmail.com
Whole thread Raw
In response to Re: Reduce pinning in btree indexes  (Kevin Grittner <kgrittn@ymail.com>)
Responses Re: Reduce pinning in btree indexes
Re: Reduce pinning in btree indexes
List pgsql-hackers
On 13 March 2015 at 15:41, Kevin Grittner <kgrittn@ymail.com> wrote:

> The feedback was generally fairly positive except for the fact that
> snapshot "age" (for purposes of being too old) was measured in
> transaction IDs assigned.  There seemed to be a pretty universal
> feeling that this needed to be changed to a time-based setting.

-1 for a time based setting.

After years of consideration, bloat is now controllable by altering
the size of the undo tablespace.

I think PostgreSQL needs something size-based also. It would need some
estimation to get it to work like that, true, but it is actually the
size of the bloat we care about, not the time. So we should be
thinking in terms of limits that we actually care about.

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, RemoteDBA, Training &
Services



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Reduce pinning in btree indexes
Next
From: Tom Lane
Date:
Subject: ranlib bleating about dirmod.o being empty