Re: autovacuum scheduling starvation and frenzy - Mailing list pgsql-hackers

From Tom Lane
Subject Re: autovacuum scheduling starvation and frenzy
Date
Msg-id 17728.1403565541@sss.pgh.pa.us
Whole thread Raw
In response to Re: autovacuum scheduling starvation and frenzy  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: autovacuum scheduling starvation and frenzy  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Jeff Janes <jeff.janes@gmail.com> writes:
> I didn't add this patch to the commitfest, because it was just a point
> for discussion and not actually proposed for application.  But It
> doesn't seem to have provoked much discussion either.

> Should I go add this to the next commitfest?

> I do see it listed as a resolved item in
> https://wiki.postgresql.org/wiki/PostgreSQL_9.4_Open_Items

> But I can't find a commit that would resolve it, so does that mean the
> resolution was that the behavior was not new in 9.4 and so didn't need
> to be fixed for it?

It looks to me like Robert added that item to the "open items" page,
but he put it at the bottom --- ie in the "already resolved items"
list:

https://wiki.postgresql.org/index.php?title=PostgreSQL_9.4_Open_Items&diff=22417&oldid=22380

Probably this was a mistake and it should have gone into the still-to-do
list.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Fabrízio de Royes Mello
Date:
Subject: Re: How about a proper TEMPORARY TABLESPACE?
Next
From: Tom Lane
Date:
Subject: Re: [BUGS] BUG #10728: json_to_recordset with nested json objects NULLs columns