Re: [HACKERS] Incorrect documentation about pg_stat_activity

Поиск
Список
Период
Сортировка
От Ashutosh Bapat
Тема Re: [HACKERS] Incorrect documentation about pg_stat_activity
Дата
Msg-id CAFjFpRfqMkCHwqiL4WQz1ujR5EkrVwkDFLHRX=x3ZWwPooVVQw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Incorrect documentation about pg_stat_activity  (Simon Riggs <simon@2ndquadrant.com>)
Ответы Re: [HACKERS] Incorrect documentation about pg_stat_activity  (Yugo Nagata <nagata@sraoss.co.jp>)
Список pgsql-hackers
On Wed, Jun 21, 2017 at 7:48 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
> On 21 June 2017 at 16:15, Yugo Nagata <nagata@sraoss.co.jp> wrote:
>> On Wed, 21 Jun 2017 19:08:35 +0530
>> Kuntal Ghosh <kuntalghosh.2007@gmail.com> wrote:
>>
>>> On Wed, Jun 21, 2017 at 6:05 PM, Yugo Nagata <nagata@sraoss.co.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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Sokolov Yura
Дата:
Сообщение: Re: [HACKERS] An attempt to reduce WALWriteLock contention
Следующее
От: Kunshchikov Vladimir
Дата:
Сообщение: [HACKERS] [patch] pg_dump/pg_restore zerror() and strerror() mishap