From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pgsql: Compute XID horizon for page level index vacuum on primary. |
Date: | 2019-05-01 16:34:04 |
Message-ID: | CA+Tgmobv3HhQGe7mq9OkEiaXvqahccWgXQb3YtPH4o2EqJu3Ow@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Wed, May 1, 2019 at 12:15 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2019-04-01 18:26:59 -0700, Andres Freund wrote:
> > I'm not yet convinced it's necessary to create a new GUC, but also not
> > strongly opposed. I've created an open items issue for it, so we don't
> > forget.
>
> My current inclination is to not do anything for v12. Robert, do you
> disagree?
Not strongly enough to argue about it very hard. The current behavior
is a little weird, but it's a long way from being the weirdest thing
we ship, and it appears that we have no tangible evidence that it
causes a problem in practice.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-05-01 16:50:16 | Re: pgsql: Compute XID horizon for page level index vacuum on primary. |
Previous Message | Andres Freund | 2019-05-01 16:15:06 | Re: pgsql: Compute XID horizon for page level index vacuum on primary. |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-05-01 16:38:01 | Re: using index or check in ALTER TABLE SET NOT NULL |
Previous Message | Tom Lane | 2019-05-01 16:20:22 | Re: REINDEX INDEX results in a crash for an index of pg_class since 9.6 |