Re: Open Item: Should non-text EXPLAIN always show properties?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: James Coleman <jtc331(at)gmail(dot)com>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>
Subject: Re: Open Item: Should non-text EXPLAIN always show properties?
Date: 2020-06-25 15:34:42
Message-ID: CA+TgmobC_bLsMqx9xUZbb4HOOqoEbfx4-z0O0atp5mLUoUHTXw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jun 25, 2020 at 8:42 AM James Coleman <jtc331(at)gmail(dot)com> wrote:
> Yesterday I'd replied [1] to Justin's proposal for this WRT
> incremental sort and expressed my opinion that including both
> unnecessarily (i.e., including disk when an in-memory sort was used)
> is undesirable and confusing and leads to shortcuts I believe to be
> bad habits when using the data programmatically.

+1.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2020-06-25 15:36:22 Re: PostgreSQL and big data - FDW
Previous Message Robert Haas 2020-06-25 15:33:20 Re: Parallel Seq Scan vs kernel read ahead