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

Commitc0782a1

Browse files
committed
Doc: remove claim that hash index creation depends on effective_cache_size.
This text was added by commitff21323, and not long thereafter obsoletedby commit4adc2f7 (which made the test depend on NBuffers instead); butnobody noticed the need for an update. Commit9563d5b adds some furtherdependency on maintenance_work_mem, but the existing verbiage seems tocover that with about as much precision as we really want here. Let'sjust take it all out rather than leaving ourselves open to more errors ofomission in future. (That solution makes this change back-patchable, too.)Noted by Peter Geoghegan.Discussion: <CAM3SWZRVANbj9GA9j40fAwheQCZQtSwqTN1GBTVwRrRbmSf7cg@mail.gmail.com>
1 parentb57a0a9 commitc0782a1

File tree

1 file changed

+1
-10
lines changed

1 file changed

+1
-10
lines changed

‎doc/src/sgml/ref/create_index.sgml

Lines changed: 1 addition & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -568,16 +568,7 @@ Indexes:
568568
dependent on the setting of <xref linkend="guc-maintenance-work-mem">.
569569
Larger values will reduce the time needed for index creation, so long
570570
as you don't make it larger than the amount of memory really available,
571-
which would drive the machine into swapping. For hash indexes, the
572-
value of <xref linkend="guc-effective-cache-size"> is also relevant to
573-
index creation time: <productname>PostgreSQL</productname> will use one
574-
of two different hash index creation methods depending on whether the
575-
estimated index size is more or less than <varname>effective_cache_size</>.
576-
For best results, make sure that this parameter is also set to something
577-
reflective of available memory, and be careful that the sum of
578-
<varname>maintenance_work_mem</> and <varname>effective_cache_size</> is
579-
less than the machine's RAM less whatever space is needed by other
580-
programs.
571+
which would drive the machine into swapping.
581572
</para>
582573

583574
<para>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp