Re: [PATCH v2] Progress command to monitor progression of long running SQL queries

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Remi Colinet <remi(dot)colinet(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH v2] Progress command to monitor progression of long running SQL queries
Date: 2017-05-16 17:26:14
Message-ID: CA+Tgmoa25ya7mACUZitcVwxX=uom=J-=LDsTNw-_9ScRFr984A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 16, 2017 at 2:17 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> Perhaps DSM? It is not user-friendly to fail sporadically...

Yeah. I've been thinking we might want to give each backend a
backend-lifetime DSA that is created on first use. That could be
useful for some parallel query stuff and maybe for this as well.
Other backends could attach to it to read data from it, and it would
go away on last detach (which would normally be the detach by the
creating backend, but not if somebody else happens to be reading at
the moment the backend exits).

--
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-05-16 17:29:59 Re: COPY FROM STDIN behaviour on end-of-file
Previous Message Robert Haas 2017-05-16 17:23:13 Re: [POC] hash partitioning