aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMagnus Hagander <magnus@hagander.net>2015-08-31 14:07:17 +0200
committerMagnus Hagander <magnus@hagander.net>2015-08-31 14:07:17 +0200
commit93370076c40730ce2a9071c6a4694d6b0e5b2f0c (patch)
treef6b4a48d6073d4a6a865602e2ac5fbbe8e06db77
parent0f19d0f12fa235c6951ff431bd60da594356a1a6 (diff)
downloadpostgresql-93370076c40730ce2a9071c6a4694d6b0e5b2f0c.tar.gz
postgresql-93370076c40730ce2a9071c6a4694d6b0e5b2f0c.zip
Small grammar fix
Josh Kupershmidt
-rw-r--r--doc/src/sgml/pgprewarm.sgml8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/src/sgml/pgprewarm.sgml b/doc/src/sgml/pgprewarm.sgml
index 2989ac393ed..c090401eca6 100644
--- a/doc/src/sgml/pgprewarm.sgml
+++ b/doc/src/sgml/pgprewarm.sgml
@@ -50,10 +50,10 @@ pg_prewarm(regclass, mode text default 'buffer', fork text default 'main',
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.
+ 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>