public inbox for [email protected]
help / color / mirror / Atom feedFrom: Amit Langote <[email protected]>
To: PostgreSQL-development <[email protected]>
To: [email protected] <[email protected]>
Subject: Re: Typo in doc/src/sgml/monitoring.sgml? s/tranche/trance?
Date: Wed, 23 Apr 2014 18:19:10 +0900
Message-ID: <CA+HiwqH8y_rkw4PCazJs027YfLTRinex6cwWN4B3fza5EB4pfw@mail.gmail.com> (raw)
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-hackers>
On Wed, Apr 23, 2014 at 6:15 PM, Amit Langote <[email protected]> wrote:
> Hi,
>
> Attached fixes a typo in doc/src/sgml/monitoring.sgml.
>
Sorry, typo in subject (kinda ironic!); I meant "s/trance/tranche?"
Patch attached again.
--
Amit
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Attachments:
[application/octet-stream] docs-monitoring-lwlock-tranche-not-trance-fix.patch (2.8K, 2-docs-monitoring-lwlock-tranche-not-trance-fix.patch)
download | inline diff:
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 958acc4..ffdf0c5 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -2300,7 +2300,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<entry>(char *, int, LWLockMode)</entry>
<entry>Probe that fires when an LWLock has been acquired.
arg0 is the LWLock's tranche.
- arg1 is the LWLock's offset within its trance.
+ arg1 is the LWLock's offset within its tranche.
arg2 is the requested lock mode, either exclusive or shared.</entry>
</row>
<row>
@@ -2309,7 +2309,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<entry>Probe that fires when an LWLock has been released (but note
that any released waiters have not yet been awakened).
arg0 is the LWLock's tranche.
- arg1 is the LWLock's offset within its trance.</entry>
+ arg1 is the LWLock's offset within its tranche.</entry>
</row>
<row>
<entry>lwlock-wait-start</entry>
@@ -2317,7 +2317,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<entry>Probe that fires when an LWLock was not immediately available and
a server process has begun to wait for the lock to become available.
arg0 is the LWLock's tranche.
- arg1 is the LWLock's offset within its trance.
+ arg1 is the LWLock's offset within its tranche.
arg2 is the requested lock mode, either exclusive or shared.</entry>
</row>
<row>
@@ -2326,7 +2326,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<entry>Probe that fires when a server process has been released from its
wait for an LWLock (it does not actually have the lock yet).
arg0 is the LWLock's tranche.
- arg1 is the LWLock's offset within its trance.
+ arg1 is the LWLock's offset within its tranche.
arg2 is the requested lock mode, either exclusive or shared.</entry>
</row>
<row>
@@ -2335,7 +2335,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<entry>Probe that fires when an LWLock was successfully acquired when the
caller specified no waiting.
arg0 is the LWLock's tranche.
- arg1 is the LWLock's offset within its trance.
+ arg1 is the LWLock's offset within its tranche.
arg2 is the requested lock mode, either exclusive or shared.</entry>
</row>
<row>
@@ -2344,7 +2344,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<entry>Probe that fires when an LWLock was not successfully acquired when
the caller specified no waiting.
arg0 is the LWLock's tranche.
- arg1 is the LWLock's offset within its trance.
+ arg1 is the LWLock's offset within its tranche.
arg2 is the requested lock mode, either exclusive or shared.</entry>
</row>
<row>
view thread (3+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Typo in doc/src/sgml/monitoring.sgml? s/tranche/trance?
In-Reply-To: <CA+HiwqH8y_rkw4PCazJs027YfLTRinex6cwWN4B3fza5EB4pfw@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox