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

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Remi Colinet <remi(dot)colinet(at)gmail(dot)com>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Robert Haas <robertmhaas(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:11:55
Message-ID: CAB7nPqSNqdayo3b5rg1osX=MGtGPC5EOnJs2aaJraqrUCvZHYw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 1, 2017 at 6:35 PM, Remi Colinet <remi(dot)colinet(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2017-08-01 17:17:02 Re: [PATCH v3] pg_progress() SQL function to monitor progression of long running SQL queries/utilities
Previous Message Tom Lane 2017-08-01 16:58:50 Re: [GENERAL] Not able to create collation on Windows