Re: [PATCH v3] pg_progress() SQL function to monitor progression of long running SQL queries/utilities

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Remi Colinet <remi(dot)colinet(at)gmail(dot)com>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH v3] pg_progress() SQL function to monitor progression of long running SQL queries/utilities
Date: 2017-08-01 17:57:12
Message-ID: CA+TgmoZVVQm0w1V2Rj5qL__Kod44G8UPd6+wxL+CfAsYLFQzRw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 1, 2017 at 12:35 PM, Remi Colinet <remi(dot)colinet(at)gmail(dot)com> wrote:
> I did it in version 2 of the patch.
> I'am skeptical about the use of JSON, XML, and others in such output.
>
> Does anyone use these formats (XML, JSON, YAML) for EXPLAIN output?
> I suspect only TEXT format is being used.

Do you have any reason to suspect that others aren't being used? The
default format for anything is likely to be the most commonly-used
one, but I don't think that proves the others are unused.

Even if it were true, it wouldn't be a good justification for
inventing an entirely new machine-readable format, at least not IMHO.

--
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 Tom Lane 2017-08-01 17:57:42 Re: Better way to handle suppression of CASCADE detail messages
Previous Message Robert Haas 2017-08-01 17:54:42 Re: A bug in mapping attributes in ATExecAttachPartition()