Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit05cd021

Browse files
committed
Remove tabs from SGML source files.
1 parentef23a77 commit05cd021

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

‎doc/src/sgml/maintenance.sgml

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.71 2007/04/16 18:29:50 alvherre Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.72 2007/04/18 20:44:53 momjian Exp $ -->
22

33
<chapter id="maintenance">
44
<title>Routine Database Maintenance Tasks</title>
@@ -481,11 +481,11 @@ HINT: Stop the postmaster and use a standalone backend to VACUUM in "mydb".
481481
</para>
482482

483483
<para>
484-
Beginning in <productname>PostgreSQL</productname> 8.3, autovacuum has a
485-
multi-process architecture: there is a daemon process, called the
486-
<firstterm>autovacuum launcher</firstterm>, which is in charge of starting
487-
an <firstterm>autovacuum worker</firstterm> process on each database every
488-
<xref linkend="guc-autovacuum-naptime"> seconds.
484+
Beginning in <productname>PostgreSQL</productname> 8.3, autovacuum has a
485+
multi-process architecture: there is a daemon process, called the
486+
<firstterm>autovacuum launcher</firstterm>, which is in charge of starting
487+
an <firstterm>autovacuum worker</firstterm> process on each database every
488+
<xref linkend="guc-autovacuum-naptime"> seconds.
489489
</para>
490490

491491
<para>
@@ -494,11 +494,11 @@ HINT: Stop the postmaster and use a standalone backend to VACUUM in "mydb".
494494
and <command>ANALYZE</> work to do takes too long to run, the deadline may
495495
be failed to meet for other databases. Also, if a particular database
496496
takes long to process, more than one worker may be processing it
497-
simultaneously. The workers are smart enough to avoid repeating work that
498-
other workers have done, so this is normally not a problem. Note that the
499-
number of running workers does not count towards the <xref
500-
linkend="guc-max-connections"> nor the <xref
501-
linkend="guc-superuser-reserved-connections"> limits.
497+
simultaneously. The workers are smart enough to avoid repeating work that
498+
other workers have done, so this is normally not a problem. Note that the
499+
number of running workers does not count towards the <xref
500+
linkend="guc-max-connections"> nor the <xref
501+
linkend="guc-superuser-reserved-connections"> limits.
502502
</para>
503503

504504
<para>

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp