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

From Andres Freund
Subject Re: [HACKERS] [PATCH v3] pg_progress() SQL function to monitorprogression of long running SQL queries/utilities
Date
Msg-id 20170801171702.24f5tdtv7trw6raw@alap3.anarazel.de
Whole thread Raw
In response to Re: [HACKERS] [PATCH v3] pg_progress() SQL function to monitorprogression of long running SQL queries/utilities  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: [HACKERS] [PATCH v3] pg_progress() SQL function to monitorprogression of long running SQL queries/utilities  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On 2017-08-01 19:11:55 +0200, Michael Paquier wrote:
> 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.

Hm? e.d.c accepts the text explain format, so I'm unclear on what you're
saying here.

Andres



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] [PATCH v3] pg_progress() SQL function to monitorprogression of long running SQL queries/utilities
Next
From: Tom Lane
Date:
Subject: [HACKERS] Better way to handle suppression of CASCADE detail messages