Re: Incorrect documentation about pg_stat_activity

From: Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>, Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Incorrect documentation about pg_stat_activity
Date: 2017-06-22 08:44:53
Message-ID: CAFjFpRfqMkCHwqiL4WQz1ujR5EkrVwkDFLHRX=x3ZWwPooVVQw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jun 21, 2017 at 7:48 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On 21 June 2017 at 16:15, Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp> wrote:
>> On Wed, 21 Jun 2017 19:08:35 +0530
>> Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com> wrote:
>>
>>> On Wed, Jun 21, 2017 at 6:05 PM, Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp> wrote:
>>> >
>>> > Attached is a patch for the documentation fix.
>>> >
>>> Please attach the patch as well. :-)
>>
>> I'm sorry, I forgot it. I attahed this.
>
> Thanks, will apply.

The patch is adjusting documentation for the observed behaviour. But I
don't see a justification as to why the observed behaviour is correct
one? Was there a commit which allowed startup process to be part of
pg_stat_activity but forgot to update the documentation or the current
behaviour is unintentional and probably needs to be fixed?

--
Best Wishes,
Ashutosh Bapat
EnterpriseDB Corporation
The Postgres Database Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kunshchikov Vladimir 2017-06-22 08:46:21 [patch] pg_dump/pg_restore zerror() and strerror() mishap
Previous Message Sokolov Yura 2017-06-22 08:42:43 Re: An attempt to reduce WALWriteLock contention