| From: | Christopher Kings-Lynne <chris(dot)kings-lynne(at)calorieking(dot)com> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Neil Conway <neilc(at)samurai(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Progress bar updates |
| Date: | 2006-07-20 01:39:21 |
| Message-ID: | 44BEDEC9.7000300@calorieking.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> It would be the most practical way for a DBA to monitor an application. But
> it's not going to be convenient for clients like pgadmin or psql. Even a web
> server may want to, for example, stream ajax code updating a progress bar
> until it has results and then stream the ajax to display the results. Having
> to get the backend pid before your query and then open a second database
> connection to monitor your first connection would be extra footwork for
> nothing.
But that said, it CAN be coded and work just fine no?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-07-20 02:19:36 | Re: pg_regress breaks on msys |
| Previous Message | Andrew Dunstan | 2006-07-20 01:07:03 | Re: pg_regress breaks on msys |