| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: RFC: replace pg_stat_activity.waiting with something more descriptive |
| Date: | 2015-06-22 21:22:39 |
| Message-ID: | 24985.1435008159@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> On Mon, Jun 22, 2015 at 12:37 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> ... The basic idea is that pg_stat_activity.waiting would be
>> replaced by a new column pg_stat_activity.wait_event, which would
>> display the reason why that backend is waiting.
> Instead of changing the column, can't we add a new one? Adjusting
> columns in PSA requires the innumerable queries written against it to
> be adjusted along with all the wiki instructions to dev ops for
> emergency stuck query detection etc etc.
+1. Removing the boolean column seems like it will arbitrarily break
a whole lot of client-side code, for not-very-adequate reasons.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-06-22 21:31:05 | Re: NULL passed as an argument to memcmp() in parse_func.c |
| Previous Message | Rajeev rastogi | 2015-06-22 21:14:01 | Re: 9.5 release notes |