Re: [HACKERS] [PATCH v3] pg_progress() SQL function to monitorprogression of long running SQL queries/utilities - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [HACKERS] [PATCH v3] pg_progress() SQL function to monitorprogression of long running SQL queries/utilities
Date
Msg-id CAB7nPqSNqdayo3b5rg1osX=MGtGPC5EOnJs2aaJraqrUCvZHYw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] [PATCH v3] pg_progress() SQL function to monitorprogression of long running SQL queries/utilities  (Remi Colinet <remi.colinet@gmail.com>)
Responses Re: [HACKERS] [PATCH v3] pg_progress() SQL function to monitorprogression of long running SQL queries/utilities  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Tue, Aug 1, 2017 at 6:35 PM, Remi Colinet <remi.colinet@gmail.com> wrote:
> I'am skeptical about the use of JSON, XML, and others in such output.

You should not.

> Does anyone use these formats (XML, JSON, YAML) for EXPLAIN output?
> I suspect only TEXT format is being used.

I think that Depesz makes use of a non-default format for its
explain.depesz.com, or he would have a hard time maintaining a
deparsing API for its application. JSON is for example easy to extract
and reformat when doing analysis of the inner planner nodes, and
Postgres has json and xml data types, which makes analysis with SQL
even easier sometimes.
-- 
Michael



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] [GENERAL] Not able to create collation on Windows
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] [PATCH v3] pg_progress() SQL function to monitorprogression of long running SQL queries/utilities