From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Performance improvement for joins where outer side is unique |
Date: | 2015-09-03 16:50:37 |
Message-ID: | CA+TgmoamVYBOs+PDKvXR2Vaeoh=NrgzsDPh-mjgnH2pwD9gPwA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 503 토토 커뮤니티 페치 |
On Tue, Aug 25, 2015 at 1:25 AM, David Rowley
<david(dot)rowley(at)2ndquadrant(dot)com> wrote:
> If that's the case then why do we not enable verbose for all of the non-text
> outputs?
> It seems strange to start making exceptions on a case-by-case basis.
+1. FORMAT and VERBOSE are separate options, and each one should
control what the name suggests, not the other thing.
Also: very nice performance results.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | dinesh kumar | 2015-09-03 16:53:24 | Re: [PROPOSAL] Inputs on forcing VACUUM VERBOSE to write timestamp |
Previous Message | Shulgin, Oleksandr | 2015-09-03 16:30:54 | Re: On-demand running query plans using auto_explain and signals |