From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Ants Aasma <ants(dot)aasma(at)eesti(dot)ee>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Kevin Grittner <kgrittn(at)postgresql(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "pgsql-committers(at)postgresql(dot)org" <pgsql-committers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] Re: pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold < |
Date: | 2016-06-10 14:45:01 |
Message-ID: | CACjxUsOYGwZPJFT0VxBno7NL_26DLBdNgt9O4-YAhQHBS9WdFg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Thu, Jun 9, 2016 at 6:16 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> So I like the idea of centralizing checks in
> RelationAllowsEarlyVacuum, but shouldn't it really be called
> RelationAllowsEarlyPruning?
Since vacuum calls the pruning function, and not the other way
around, the name you suggest would be technically more correct.
Committed using "Pruning" instead of "Vacuum" in both new macros.
I have closed the CREATE INDEX versus "snapshot too old" issue in
the "PostgreSQL 9.6 Open Items" Wiki page.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-06-10 14:50:36 | Re: [COMMITTERS] pgsql: Don't generate parallel paths for rels with parallel-restricted |
Previous Message | Kevin Grittner | 2016-06-10 14:35:51 | pgsql: Fix interaction between CREATE INDEX and "snapshot too old". |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-06-10 14:50:36 | Re: [COMMITTERS] pgsql: Don't generate parallel paths for rels with parallel-restricted |
Previous Message | Craig Ringer | 2016-06-10 13:32:54 | Re: [HACKERS] Online DW |