| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net>, Alex Hunsaker <badalex(at)gmail(dot)com> |
| Subject: | Re: Progress indication prototype |
| Date: | 2010-08-17 22:29:01 |
| Message-ID: | AANLkTi=Cw4zVpYc9CZr-0gi+crr0eVzBxfwBvHw==vCF@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Aug 17, 2010 at 10:53 PM, Greg Stark <stark(at)mit(dot)edu> wrote:
> (Sorry for top posting and for any typos -- typing on my phone)
>
> In my earlier patch to do progress indicators for arbitrary SQL queries I
> had envisioned a setup similar to how we handle query cancellation. Psql
> could support a key like SIGINFO which would make it request an update.
> Clients like pgadmin would either do that periodically or set some guc or
> protocol option to request periodic updates in advance.
Which is ideal for monitoring your own connection - having the info in
the pg_stat_activity is also valuable for monitoring and system
administration. Both would be ideal :-)
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | KaiGai Kohei | 2010-08-17 23:37:24 | Re: security label support, part.2 |
| Previous Message | Greg Stark | 2010-08-17 21:53:13 | Re: Progress indication prototype |