| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Jim Nasby <jim(dot)nasby(at)openscg(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, David Steele <david(at)pgmasters(dot)net>, vinayak <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp>, David Fetter <david(at)fetter(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ANALYZE command progress checker |
| Date: | 2017-03-10 19:06:02 |
| Message-ID: | 20170310190602.dvvsjchhl6cyrqoi@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2017-03-10 02:11:18 -0600, Jim Nasby wrote:
> Perhaps instead of adding more clutter to \dvS we could just have a SRF for
> now.
I don't see that as clutter, it's useful information, and keeping it
discoverable is good, not bad.
> At over 2800 rows currently, you're not going to notice one more
> addition to \dfS.
I think it's hard to design a good SRF for this. Because the fields for
different types of progress are different / empty, you can't just
trivially return them as rows. You'd have to do some EAV like
'command, field_name1, field_value1, ...' type of thing - not
particularly pretty / easy to use.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-03-10 19:09:09 | Re: Need a builtin way to run all tests faster manner |
| Previous Message | Peter Eisentraut | 2017-03-10 19:05:42 | Re: logical replication access control patches |