Re: Top features in 9.6? - Mailing list pgsql-advocacy

From Justin Clift
Subject Re: Top features in 9.6?
Date
Msg-id 627B0619-7EBC-4787-908B-E926E4162D7E@postgresql.org
Whole thread Raw
In response to Re: Top features in 9.6?  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Top features in 9.6?  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-advocacy
On 12 Apr 2016, at 13:37, Robert Haas <robertmhaas@gmail.com> wrote:
> On Tue, Apr 12, 2016 at 3:21 AM, Magnus Hagander <magnus@hagander.net> wrote:
>> I think that may turn out to be one of those "hidden gems" of this release.
>> As in being the one that nobody talks about now, but then a few years down
>> the road it's the one that everybody talks about. But it's somewhat hard to
>> explain to people who (1) don't know how the system really works (though
>> that would count for things like snapshot too old as well) or (2) actually
>> have run into the current problem (why hey, that's also the same with
>> snapshot too old)
>
> Agreed.  Unfortunately, for many people, the first time they really
> become aware of autovacuum is when all of their tables hit the freeze
> threshold for the first time.  And this doesn't help with that.  You
> still have to scan everything after 200 million transactions; it's
> just that you no longer have to do it again every 200 million
> transactions after that.  I still think it's a great feature, though.

Er... we don't provide a warning ahead of time in the logs or something?

+ Justin

--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi



pgsql-advocacy by date:

Previous
From: Robert Haas
Date:
Subject: Re: Top features in 9.6?
Next
From: Robert Haas
Date:
Subject: Re: Top features in 9.6?