Skip site navigation (1) Skip section navigation (2)

Re: Documentation of pg_badkend_pid and stats functions

From: Jim Nasby <decibel(at)decibel(dot)org>
To: Jim Nasby <decibel(at)decibel(dot)org>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-docs(at)postgresql(dot)org
Subject: Re: Documentation of pg_badkend_pid and stats functions
Date: 2007-05-13 20:55:54
Message-ID: 827EEEAA-A2B0-4AE4-9D51-96524E05CFC1@decibel.org (view raw or flat)
Thread:
Lists: pgsql-docs
On May 7, 2007, at 11:03 AM, Jim Nasby wrote:
> On May 6, 2007, at 11:44 AM, Bruce Momjian wrote:
>> Jim Nasby wrote:
>>> On Apr 12, 2007, at 7:54 AM, Jim Nasby wrote:
>>>> Two questions: Why is pg_backend_pid documented with the stats
>>>> functions (9.19 System Information Functions) seems more logical.
>>>>
>>>> Also, I can see mentioning the stats functions in the monitoring
>>>> section, but shouldn't they actually be documented in with the rest
>>>> of the functions?
>>>
>>> No comments? Does that mean if I write up a patch it'll be accepted?
>>
>> Yea, I was wondering about that.  I think the best idea would be to
>> reference the backend functions from the main functions page, rather
>> than move them.
>
> Well, pg_backend_pid makes no sense being in with the stats  
> functions, so I'll move it. I'll just include references to the  
> other stuff.

Turns out it didn't really make much more sense to move  
pg_backend_pid either, so I went with Bruce's original idea.

Attachment: monfunc.patch
Description: application/octet-stream (847 bytes)

In response to

Responses

pgsql-docs by date

Next:From: David FetterDate: 2007-05-13 21:15:26
Subject: OS/X startup scripts
Previous:From: Jeff DavisDate: 2007-05-09 17:19:05
Subject: Re: PITR and tar

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group