From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
---|---|
To: | Vladimir Borodin <root(at)simply(dot)name> |
Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Background Processes and reporting |
Date: | 2016-03-14 15:12:12 |
Message-ID: | CACjxUsMwha4eWqiAfOpMXDRKMQftFi+=cY7P5v57cEsS94bF4A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Mar 12, 2016 at 11:40 AM, Vladimir Borodin <root(at)simply(dot)name> wrote:
> 12 марта 2016 г., в 13:59, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> написал(а):
>> I think here another point which needs more thoughts is that many of the
>> pg_stat_activity fields are not relevant for background processes, ofcourse
>> one can say that we can keep those fields as NULL, but still I think that
>> indicates it is not the most suitable way to expose such information.
>>
>> Another way could be to have new view like pg_stat_background_activity with
>> only relevant fields or try expose via individual views like
>> pg_stat_bgwriter.
>
> From the DBA point of view it is much more convenient to see all wait events
> in one view. I don’t know if it is right to break compability even more, but
> IMHO exposing this data in different views is a bad plan.
+1
If they are split into separate views I think that there will be a
lot of effort put into views to present the UNION of them, probably
with weird corner cases and race conditions. A single view can
probably better manage race conditions, and a WHERE clause is not
as tricky for the DBA and/or end user.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | David Steele | 2016-03-14 15:32:31 | Re: Password identifiers, protocol aging and SCRAM protocol |
Previous Message | Dagfinn Ilmari =?utf-8?Q?Manns=C3=A5ker?= | 2016-03-14 14:55:39 | [PATCH] Use correct types and limits for PL/Perl SPI query results |