mirror of
				https://github.com/postgres/postgres.git
				synced 2025-10-31 00:03:57 -04:00 
			
		
		
		
	Doc: fix a few oddly-spelled SGML ID attributes.
Avoid use of "_" in SGML IDs. Awhile back that was actually disallowed by the toolchain, as a consequence of which our convention has been to use "-" instead. Fix a couple of stragglers that are particularly inconsistent with that convention and with related IDs. This is just neatnik-ism, so no need for back-patch. Discussion: https://postgr.es/m/769446.1673478332@sss.pgh.pa.us
This commit is contained in:
		
							parent
							
								
									27da598961
								
							
						
					
					
						commit
						09d465c397
					
				| @ -6062,7 +6062,7 @@ SELECT * FROM parent WHERE key = 2400; | ||||
|       </listitem> | ||||
|      </varlistentry> | ||||
| 
 | ||||
|      <varlistentry id="guc-plan-cache_mode" xreflabel="plan_cache_mode"> | ||||
|      <varlistentry id="guc-plan-cache-mode" xreflabel="plan_cache_mode"> | ||||
|       <term><varname>plan_cache_mode</varname> (<type>enum</type>) | ||||
|       <indexterm> | ||||
|        <primary><varname>plan_cache_mode</varname> configuration parameter</primary> | ||||
|  | ||||
| @ -183,10 +183,10 @@ | ||||
|   <title>The <function>pg_buffercache_summary()</function> Function</title> | ||||
| 
 | ||||
|   <para> | ||||
|    The definitions of the columns exposed by the function are shown in <xref linkend="pgbuffercache_summary-columns"/>. | ||||
|    The definitions of the columns exposed by the function are shown in <xref linkend="pgbuffercache-summary-columns"/>. | ||||
|   </para> | ||||
| 
 | ||||
|   <table id="pgbuffercache_summary-columns"> | ||||
|   <table id="pgbuffercache-summary-columns"> | ||||
|    <title><function>pg_buffercache_summary()</function> Output Columns</title> | ||||
|    <tgroup cols="1"> | ||||
|     <thead> | ||||
|  | ||||
| @ -33,7 +33,7 @@ PostgreSQL documentation | ||||
|   </cmdsynopsis> | ||||
|  </refsynopsisdiv> | ||||
| 
 | ||||
|  <refsect1 id="r1-app-pg_checksums-1"> | ||||
|  <refsect1 id="r1-app-pgchecksums-1"> | ||||
|   <title>Description</title> | ||||
|   <para> | ||||
|    <application>pg_checksums</application> checks, enables or disables data | ||||
|  | ||||
| @ -139,7 +139,7 @@ PREPARE <replaceable class="parameter">name</replaceable> [ ( <replaceable class | ||||
|   </para> | ||||
| 
 | ||||
|   <para> | ||||
|    By default (that is, when <xref linkend="guc-plan-cache_mode"/> is set | ||||
|    By default (that is, when <xref linkend="guc-plan-cache-mode"/> is set | ||||
|    to <literal>auto</literal>), the server will automatically choose | ||||
|    whether to use a generic or custom plan for a prepared statement that | ||||
|    has parameters.  The current rule for this is that the first five | ||||
|  | ||||
		Loading…
	
	
			
			x
			
			
		
	
		Reference in New Issue
	
	Block a user