Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 71A5D1A04809 for ; Mon, 5 Dec 2011 23:36:23 -0400 (AST) Received: from oproxy6-pub.bluehost.com ([67.222.54.6]) by magus.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1RXlpM-0000KA-25 for pgsql-docs@postgresql.org; Tue, 06 Dec 2011 03:36:22 +0000 Received: (qmail 12095 invoked by uid 0); 6 Dec 2011 03:35:45 -0000 Received: from unknown (HELO host159.hostmonster.com) (74.220.207.159) by cpoproxy3.bluehost.com with SMTP; 6 Dec 2011 03:35:45 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=timbira.com; s=default; h=Content-Type:Subject:To:MIME-Version:From:Date:Message-ID; bh=ny65/nkz8MF4zd91NNw9/ExJEac0fTNHW8Gt5woVjo0=; b=dwhwlbOBZRwd+8jCmzY/2Udf0bxxz76sCJItSu1ha7MLNxuwKonBVyB1OJqpQoHqfeTi4YJc4mO8H+sA8EcmOxWZEC7ZTX8VNjyR4NQOSkbN6TRmyPMNrVm/9TWWEzqE; Received: from 201-10-138-156.gnace701.dsl.brasiltelecom.net.br ([201.10.138.156] helo=[10.3.2.2]) by host159.hostmonster.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1RXlom-0001xj-Ke for pgsql-docs@postgresql.org; Mon, 05 Dec 2011 20:35:44 -0700 Message-ID: <4EDD8D24.7060405@timbira.com> Date: Tue, 06 Dec 2011 00:33:56 -0300 From: Euler Taveira de Oliveira User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111114 Icedove/3.1.16 MIME-Version: 1.0 To: PostgreSQL-documentation Subject: pg_stat_get_wal_senders documented X-Enigmail-Version: 1.1.2 Content-Type: multipart/mixed; boundary="------------060603060007090002030605" X-Identified-User: {1651:host159.hostmonster.com:timbirac:timbira.com} {sentby:smtp auth 201.10.138.156 authed with euler@timbira.com} X-Pg-Spam-Score: -2.0 (--) X-Archive-Number: 201112/14 X-Sequence-Number: 7121 This is a multi-part message in MIME format. --------------060603060007090002030605 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi, Is $SUBJECT an oversight? I noticed that pg_stat_get_activity (function behind pg_stat_activity) is documented so for consistency, function pg_stat_get_wal_senders (function behind pg_stat_replication) should be documented too. Patch is attached. -- Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/ PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento --------------060603060007090002030605 Content-Type: text/x-patch; name="doc.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="doc.patch" diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index b9dc1d2..d6056a2 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -1182,6 +1182,15 @@ postgres: user database host + pg_stat_get_wal_senders() + setof record + + One record for each active wal sender. The fields returned are a subset + of those in the pg_stat_replication view. + + + + pg_stat_clear_snapshot() void --------------060603060007090002030605--