From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
Cc: | Pavel Golub <pavel(at)gf(dot)microolap(dot)com>, Darafei Praliaskouski <me(at)komzpa(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: GUC for cleanup indexes threshold. |
Date: | 2017-10-31 09:22:54 |
Message-ID: | CA+TgmoYZ6+=8ps=cikv2gKO=QUpoMRjj1qnuXMtMPKrp7r+6sQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Oct 16, 2017 at 3:02 PM, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
> I guess that is the patch I proposed. However I think that there still
> is room for discussion because the patch cannot skip to cleanup vacuum
> when aggressive vacuum, which is one of the situation that I really
> wanted to skip.
Well, I think there are outstanding concerns that the patch in
question is not safe, and I don't see that anything has been done to
resolve them.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2017-10-31 09:25:04 | Re: MERGE SQL Statement for PG11 |
Previous Message | Robert Haas | 2017-10-31 09:20:09 | Re: ERROR: MultiXactId 3268957 has not been created yet -- apparent wraparound after missused pg_resetxlogs |