public inbox for [email protected]  
help / color / mirror / Atom feed
From: Josh Kupershmidt <[email protected]>
To: pgsql-docs <[email protected]>
Subject: small fix for pgprewarm.sgml
Date: Wed, 26 Aug 2015 19:12:28 -0400
Message-ID: <CAK3UJRHxwac4SqnTRiKoyBk4QqEKk6h0B1KtuU3nfv_gk8cPWA@mail.gmail.com> (raw)
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-docs>

Attached is a small grammar fix for the pg_prewarm doc page.

Josh

diff --git a/doc/src/sgml/pgprewarm.sgml b/doc/src/sgml/pgprewarm.sgml
new file mode 100644
index 2989ac3..c090401
*** a/doc/src/sgml/pgprewarm.sgml
--- b/doc/src/sgml/pgprewarm.sgml
*************** pg_prewarm(regclass, mode text default '
*** 50,59 ****
     using <literal>buffer</literal> &mdash; will likely result in lower-numbered
     blocks being evicted as higher numbered blocks are read in.  Prewarmed data
     also enjoys no special protection from cache evictions, so it is possible
!    for other system activity may evict the newly prewarmed blocks shortly after
!    they are read; conversely, prewarming may also evict other data from cache.
!    For these reasons, prewarming is typically most useful at startup, when
!    caches are largely empty.
    </para>
   </sect2>
  
--- 50,59 ----
     using <literal>buffer</literal> &mdash; will likely result in lower-numbered
     blocks being evicted as higher numbered blocks are read in.  Prewarmed data
     also enjoys no special protection from cache evictions, so it is possible
!    that other system activity may evict the newly prewarmed blocks shortly
!    after they are read; conversely, prewarming may also evict other data from
!    cache. For these reasons, prewarming is typically most useful at startup,
!    when caches are largely empty.
    </para>
   </sect2>
  


-- 
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs


Attachments:

  [text/plain] pgprewarm.sgml.diff (1.3K, 3-pgprewarm.sgml.diff)
  download | inline diff:
diff --git a/doc/src/sgml/pgprewarm.sgml b/doc/src/sgml/pgprewarm.sgml
new file mode 100644
index 2989ac3..c090401
*** a/doc/src/sgml/pgprewarm.sgml
--- b/doc/src/sgml/pgprewarm.sgml
*************** pg_prewarm(regclass, mode text default '
*** 50,59 ****
     using <literal>buffer</literal> &mdash; will likely result in lower-numbered
     blocks being evicted as higher numbered blocks are read in.  Prewarmed data
     also enjoys no special protection from cache evictions, so it is possible
!    for other system activity may evict the newly prewarmed blocks shortly after
!    they are read; conversely, prewarming may also evict other data from cache.
!    For these reasons, prewarming is typically most useful at startup, when
!    caches are largely empty.
    </para>
   </sect2>
  
--- 50,59 ----
     using <literal>buffer</literal> &mdash; will likely result in lower-numbered
     blocks being evicted as higher numbered blocks are read in.  Prewarmed data
     also enjoys no special protection from cache evictions, so it is possible
!    that other system activity may evict the newly prewarmed blocks shortly
!    after they are read; conversely, prewarming may also evict other data from
!    cache. For these reasons, prewarming is typically most useful at startup,
!    when caches are largely empty.
    </para>
   </sect2>
  


view thread (2+ 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]
  Subject: Re: small fix for pgprewarm.sgml
  In-Reply-To: <CAK3UJRHxwac4SqnTRiKoyBk4QqEKk6h0B1KtuU3nfv_gk8cPWA@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