1 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>VACUUM</title><link rel="stylesheet" type="text/css" href="stylesheet.css" /><link rev="made" href="pgsql-docs@lists.postgresql.org" /><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot" /><link rel="prev" href="sql-update.html" title="UPDATE" /><link rel="next" href="sql-values.html" title="VALUES" /></head><body id="docContent" class="container-fluid col-10"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="5" align="center">VACUUM</th></tr><tr><td width="10%" align="left"><a accesskey="p" href="sql-update.html" title="UPDATE">Prev</a> </td><td width="10%" align="left"><a accesskey="u" href="sql-commands.html" title="SQL Commands">Up</a></td><th width="60%" align="center">SQL Commands</th><td width="10%" align="right"><a accesskey="h" href="index.html" title="PostgreSQL 18.0 Documentation">Home</a></td><td width="10%" align="right"> <a accesskey="n" href="sql-values.html" title="VALUES">Next</a></td></tr></table><hr /></div><div class="refentry" id="SQL-VACUUM"><div class="titlepage"></div><a id="id-1.9.3.184.1" class="indexterm"></a><div class="refnamediv"><h2><span class="refentrytitle">VACUUM</span></h2><p>VACUUM — garbage-collect and optionally analyze a database</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><pre class="synopsis">
3 VACUUM [ ( <em class="replaceable"><code>option</code></em> [, ...] ) ] [ <em class="replaceable"><code>table_and_columns</code></em> [, ...] ]
5 <span class="phrase">where <em class="replaceable"><code>option</code></em> can be one of:</span>
7 FULL [ <em class="replaceable"><code>boolean</code></em> ]
8 FREEZE [ <em class="replaceable"><code>boolean</code></em> ]
9 VERBOSE [ <em class="replaceable"><code>boolean</code></em> ]
10 ANALYZE [ <em class="replaceable"><code>boolean</code></em> ]
11 DISABLE_PAGE_SKIPPING [ <em class="replaceable"><code>boolean</code></em> ]
12 SKIP_LOCKED [ <em class="replaceable"><code>boolean</code></em> ]
13 INDEX_CLEANUP { AUTO | ON | OFF }
14 PROCESS_MAIN [ <em class="replaceable"><code>boolean</code></em> ]
15 PROCESS_TOAST [ <em class="replaceable"><code>boolean</code></em> ]
16 TRUNCATE [ <em class="replaceable"><code>boolean</code></em> ]
17 PARALLEL <em class="replaceable"><code>integer</code></em>
18 SKIP_DATABASE_STATS [ <em class="replaceable"><code>boolean</code></em> ]
19 ONLY_DATABASE_STATS [ <em class="replaceable"><code>boolean</code></em> ]
20 BUFFER_USAGE_LIMIT <em class="replaceable"><code>size</code></em>
22 <span class="phrase">and <em class="replaceable"><code>table_and_columns</code></em> is:</span>
24 [ ONLY ] <em class="replaceable"><code>table_name</code></em> [ * ] [ ( <em class="replaceable"><code>column_name</code></em> [, ...] ) ]
25 </pre></div><div class="refsect1" id="id-1.9.3.184.5"><h2>Description</h2><p>
26 <code class="command">VACUUM</code> reclaims storage occupied by dead tuples.
27 In normal <span class="productname">PostgreSQL</span> operation, tuples that
28 are deleted or obsoleted by an update are not physically removed from
29 their table; they remain present until a <code class="command">VACUUM</code> is
30 done. Therefore it's necessary to do <code class="command">VACUUM</code>
31 periodically, especially on frequently-updated tables.
33 Without a <em class="replaceable"><code>table_and_columns</code></em>
34 list, <code class="command">VACUUM</code> processes every table and materialized view
35 in the current database that the current user has permission to vacuum.
36 With a list, <code class="command">VACUUM</code> processes only those table(s).
38 <code class="command">VACUUM ANALYZE</code> performs a <code class="command">VACUUM</code>
39 and then an <code class="command">ANALYZE</code> for each selected table. This
40 is a handy combination form for routine maintenance scripts. See
41 <a class="xref" href="sql-analyze.html" title="ANALYZE"><span class="refentrytitle">ANALYZE</span></a>
42 for more details about its processing.
44 Plain <code class="command">VACUUM</code> (without <code class="literal">FULL</code>) simply reclaims
46 available for re-use. This form of the command can operate in parallel
47 with normal reading and writing of the table, as an exclusive lock
48 is not obtained. However, extra space is not returned to the operating
49 system (in most cases); it's just kept available for re-use within the
50 same table. It also allows us to leverage multiple CPUs in order to process
51 indexes. This feature is known as <em class="firstterm">parallel vacuum</em>.
52 To disable this feature, one can use <code class="literal">PARALLEL</code> option and
53 specify parallel workers as zero. <code class="command">VACUUM FULL</code> rewrites
54 the entire contents of the table into a new disk file with no extra space,
55 allowing unused space to be returned to the operating system. This form is
56 much slower and requires an <code class="literal">ACCESS EXCLUSIVE</code> lock on
57 each table while it is being processed.
58 </p></div><div class="refsect1" id="id-1.9.3.184.6"><h2>Parameters</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term"><code class="literal">FULL</code></span></dt><dd><p>
59 Selects <span class="quote">“<span class="quote">full</span>”</span> vacuum, which can reclaim more
60 space, but takes much longer and exclusively locks the table.
61 This method also requires extra disk space, since it writes a
62 new copy of the table and doesn't release the old copy until
63 the operation is complete. Usually this should only be used when a
64 significant amount of space needs to be reclaimed from within the table.
65 </p></dd><dt><span class="term"><code class="literal">FREEZE</code></span></dt><dd><p>
66 Selects aggressive <span class="quote">“<span class="quote">freezing</span>”</span> of tuples.
67 Specifying <code class="literal">FREEZE</code> is equivalent to performing
68 <code class="command">VACUUM</code> with the
69 <a class="xref" href="runtime-config-vacuum.html#GUC-VACUUM-FREEZE-MIN-AGE">vacuum_freeze_min_age</a> and
70 <a class="xref" href="runtime-config-vacuum.html#GUC-VACUUM-FREEZE-TABLE-AGE">vacuum_freeze_table_age</a> parameters
71 set to zero. Aggressive freezing is always performed when the
72 table is rewritten, so this option is redundant when <code class="literal">FULL</code>
74 </p></dd><dt><span class="term"><code class="literal">VERBOSE</code></span></dt><dd><p>
75 Prints a detailed vacuum activity report for each table
76 at <code class="literal">INFO</code> level.
77 </p></dd><dt><span class="term"><code class="literal">ANALYZE</code></span></dt><dd><p>
78 Updates statistics used by the planner to determine the most
79 efficient way to execute a query.
80 </p></dd><dt><span class="term"><code class="literal">DISABLE_PAGE_SKIPPING</code></span></dt><dd><p>
81 Normally, <code class="command">VACUUM</code> will skip pages based on the <a class="link" href="routine-vacuuming.html#VACUUM-FOR-VISIBILITY-MAP" title="24.1.4. Updating the Visibility Map">visibility map</a>. Pages where
82 all tuples are known to be frozen can always be skipped, and those
83 where all tuples are known to be visible to all transactions may be
84 skipped except when performing an aggressive vacuum. Furthermore,
85 except when performing an aggressive vacuum, some pages may be skipped
86 in order to avoid waiting for other sessions to finish using them.
87 This option disables all page-skipping behavior, and is intended to
88 be used only when the contents of the visibility map are
89 suspect, which should happen only if there is a hardware or software
90 issue causing database corruption.
91 </p></dd><dt><span class="term"><code class="literal">SKIP_LOCKED</code></span></dt><dd><p>
92 Specifies that <code class="command">VACUUM</code> should not wait for any
93 conflicting locks to be released when beginning work on a relation:
94 if a relation cannot be locked immediately without waiting, the relation
95 is skipped. Note that even with this option,
96 <code class="command">VACUUM</code> may still block when opening the relation's
97 indexes. Additionally, <code class="command">VACUUM ANALYZE</code> may still
98 block when acquiring sample rows from partitions, table inheritance
99 children, and some types of foreign tables. Also, while
100 <code class="command">VACUUM</code> ordinarily processes all partitions of
101 specified partitioned tables, this option will cause
102 <code class="command">VACUUM</code> to skip all partitions if there is a
103 conflicting lock on the partitioned table.
104 </p></dd><dt><span class="term"><code class="literal">INDEX_CLEANUP</code></span></dt><dd><p>
105 Normally, <code class="command">VACUUM</code> will skip index vacuuming
106 when there are very few dead tuples in the table. The cost of
107 processing all of the table's indexes is expected to greatly
108 exceed the benefit of removing dead index tuples when this
109 happens. This option can be used to force
110 <code class="command">VACUUM</code> to process indexes when there are more
111 than zero dead tuples. The default is <code class="literal">AUTO</code>,
112 which allows <code class="command">VACUUM</code> to skip index vacuuming
113 when appropriate. If <code class="literal">INDEX_CLEANUP</code> is set to
114 <code class="literal">ON</code>, <code class="command">VACUUM</code> will
115 conservatively remove all dead tuples from indexes. This may be
116 useful for backwards compatibility with earlier releases of
117 <span class="productname">PostgreSQL</span> where this was the
120 <code class="literal">INDEX_CLEANUP</code> can also be set to
121 <code class="literal">OFF</code> to force <code class="command">VACUUM</code> to
122 <span class="emphasis"><em>always</em></span> skip index vacuuming, even when
123 there are many dead tuples in the table. This may be useful
124 when it is necessary to make <code class="command">VACUUM</code> run as
125 quickly as possible to avoid imminent transaction ID wraparound
126 (see <a class="xref" href="routine-vacuuming.html#VACUUM-FOR-WRAPAROUND" title="24.1.5. Preventing Transaction ID Wraparound Failures">Section 24.1.5</a>). However, the
127 wraparound failsafe mechanism controlled by <a class="xref" href="runtime-config-vacuum.html#GUC-VACUUM-FAILSAFE-AGE">vacuum_failsafe_age</a> will generally trigger
128 automatically to avoid transaction ID wraparound failure, and
129 should be preferred. If index cleanup is not performed
130 regularly, performance may suffer, because as the table is
131 modified indexes will accumulate dead tuples and the table
132 itself will accumulate dead line pointers that cannot be removed
133 until index cleanup is completed.
135 This option has no effect for tables that have no index and is
136 ignored if the <code class="literal">FULL</code> option is used. It also
137 has no effect on the transaction ID wraparound failsafe
138 mechanism. When triggered it will skip index vacuuming, even
139 when <code class="literal">INDEX_CLEANUP</code> is set to
140 <code class="literal">ON</code>.
141 </p></dd><dt><span class="term"><code class="literal">PROCESS_MAIN</code></span></dt><dd><p>
142 Specifies that <code class="command">VACUUM</code> should attempt to process the
143 main relation. This is usually the desired behavior and is the default.
144 Setting this option to false may be useful when it is only necessary to
145 vacuum a relation's corresponding <code class="literal">TOAST</code> table.
146 </p></dd><dt><span class="term"><code class="literal">PROCESS_TOAST</code></span></dt><dd><p>
147 Specifies that <code class="command">VACUUM</code> should attempt to process the
148 corresponding <code class="literal">TOAST</code> table for each relation, if one
149 exists. This is usually the desired behavior and is the default.
150 Setting this option to false may be useful when it is only necessary to
151 vacuum the main relation. This option is required when the
152 <code class="literal">FULL</code> option is used.
153 </p></dd><dt><span class="term"><code class="literal">TRUNCATE</code></span></dt><dd><p>
154 Specifies that <code class="command">VACUUM</code> should attempt to
155 truncate off any empty pages at the end of the table and allow
156 the disk space for the truncated pages to be returned to
157 the operating system. This is normally the desired behavior
158 and is the default unless <a class="xref" href="runtime-config-vacuum.html#GUC-VACUUM-TRUNCATE">vacuum_truncate</a>
159 is set to false or the <code class="literal">vacuum_truncate</code>
160 option has been set to false for the table to be vacuumed.
161 Setting this option to false may be useful to avoid
162 <code class="literal">ACCESS EXCLUSIVE</code> lock on the table that
163 the truncation requires. This option is ignored if the
164 <code class="literal">FULL</code> option is used.
165 </p></dd><dt><span class="term"><code class="literal">PARALLEL</code></span></dt><dd><p>
166 Perform index vacuum and index cleanup phases of <code class="command">VACUUM</code>
167 in parallel using <em class="replaceable"><code>integer</code></em>
168 background workers (for the details of each vacuum phase, please
169 refer to <a class="xref" href="progress-reporting.html#VACUUM-PHASES" title="Table 27.46. VACUUM Phases">Table 27.46</a>). The number of workers used
170 to perform the operation is equal to the number of indexes on the
171 relation that support parallel vacuum which is limited by the number of
172 workers specified with <code class="literal">PARALLEL</code> option if any which is
173 further limited by <a class="xref" href="runtime-config-resource.html#GUC-MAX-PARALLEL-MAINTENANCE-WORKERS">max_parallel_maintenance_workers</a>.
174 An index can participate in parallel vacuum if and only if the size of the
175 index is more than <a class="xref" href="runtime-config-query.html#GUC-MIN-PARALLEL-INDEX-SCAN-SIZE">min_parallel_index_scan_size</a>.
176 Please note that it is not guaranteed that the number of parallel workers
177 specified in <em class="replaceable"><code>integer</code></em> will be
178 used during execution. It is possible for a vacuum to run with fewer
179 workers than specified, or even with no workers at all. Only one worker
180 can be used per index. So parallel workers are launched only when there
181 are at least <code class="literal">2</code> indexes in the table. Workers for
182 vacuum are launched before the start of each phase and exit at the end of
183 the phase. These behaviors might change in a future release. This
184 option can't be used with the <code class="literal">FULL</code> option.
185 </p></dd><dt><span class="term"><code class="literal">SKIP_DATABASE_STATS</code></span></dt><dd><p>
186 Specifies that <code class="command">VACUUM</code> should skip updating the
187 database-wide statistics about oldest unfrozen XIDs. Normally
188 <code class="command">VACUUM</code> will update these statistics once at the
189 end of the command. However, this can take awhile in a database
190 with a very large number of tables, and it will accomplish nothing
191 unless the table that had contained the oldest unfrozen XID was
192 among those vacuumed. Moreover, if multiple <code class="command">VACUUM</code>
193 commands are issued in parallel, only one of them can update the
194 database-wide statistics at a time. Therefore, if an application
195 intends to issue a series of many <code class="command">VACUUM</code>
196 commands, it can be helpful to set this option in all but the last
197 such command; or set it in all the commands and separately
198 issue <code class="literal">VACUUM (ONLY_DATABASE_STATS)</code> afterwards.
199 </p></dd><dt><span class="term"><code class="literal">ONLY_DATABASE_STATS</code></span></dt><dd><p>
200 Specifies that <code class="command">VACUUM</code> should do nothing except
201 update the database-wide statistics about oldest unfrozen XIDs.
202 When this option is specified,
203 the <em class="replaceable"><code>table_and_columns</code></em>
204 list must be empty, and no other option may be enabled
205 except <code class="literal">VERBOSE</code>.
206 </p></dd><dt><span class="term"><code class="literal">BUFFER_USAGE_LIMIT</code></span></dt><dd><p>
208 <a class="glossterm" href="glossary.html#GLOSSARY-BUFFER-ACCESS-STRATEGY"><em class="glossterm"><a class="glossterm" href="glossary.html#GLOSSARY-BUFFER-ACCESS-STRATEGY" title="Buffer Access Strategy">Buffer Access Strategy</a></em></a>
209 ring buffer size for <code class="command">VACUUM</code>. This size is used to
210 calculate the number of shared buffers which will be reused as part of
211 this strategy. <code class="literal">0</code> disables use of a
212 <code class="literal">Buffer Access Strategy</code>. If <code class="option">ANALYZE</code>
213 is also specified, the <code class="option">BUFFER_USAGE_LIMIT</code> value is used
214 for both the vacuum and analyze stages. This option can't be used with
215 the <code class="option">FULL</code> option except if <code class="option">ANALYZE</code> is
216 also specified. When this option is not specified,
217 <code class="command">VACUUM</code> uses the value from
218 <a class="xref" href="runtime-config-resource.html#GUC-VACUUM-BUFFER-USAGE-LIMIT">vacuum_buffer_usage_limit</a>. Higher settings can
219 allow <code class="command">VACUUM</code> to run more quickly, but having too
220 large a setting may cause too many other useful pages to be evicted from
221 shared buffers. The minimum value is <code class="literal">128 kB</code> and the
222 maximum value is <code class="literal">16 GB</code>.
223 </p></dd><dt><span class="term"><em class="replaceable"><code>boolean</code></em></span></dt><dd><p>
224 Specifies whether the selected option should be turned on or off.
225 You can write <code class="literal">TRUE</code>, <code class="literal">ON</code>, or
226 <code class="literal">1</code> to enable the option, and <code class="literal">FALSE</code>,
227 <code class="literal">OFF</code>, or <code class="literal">0</code> to disable it. The
228 <em class="replaceable"><code>boolean</code></em> value can also
229 be omitted, in which case <code class="literal">TRUE</code> is assumed.
230 </p></dd><dt><span class="term"><em class="replaceable"><code>integer</code></em></span></dt><dd><p>
231 Specifies a non-negative integer value passed to the selected option.
232 </p></dd><dt><span class="term"><em class="replaceable"><code>size</code></em></span></dt><dd><p>
233 Specifies an amount of memory in kilobytes. Sizes may also be specified
234 as a string containing the numerical size followed by any one of the
235 following memory units: <code class="literal">B</code> (bytes),
236 <code class="literal">kB</code> (kilobytes), <code class="literal">MB</code> (megabytes),
237 <code class="literal">GB</code> (gigabytes), or <code class="literal">TB</code> (terabytes).
238 </p></dd><dt><span class="term"><em class="replaceable"><code>table_name</code></em></span></dt><dd><p>
239 The name (optionally schema-qualified) of a specific table or
240 materialized view to vacuum. If <code class="literal">ONLY</code> is specified
241 before the table name, only that table is vacuumed. If
242 <code class="literal">ONLY</code> is not specified, the table and all its
243 inheritance child tables or partitions (if any) are also vacuumed.
244 Optionally, <code class="literal">*</code> can be specified after the table name
245 to explicitly indicate that inheritance child tables (or partitions) are
247 </p></dd><dt><span class="term"><em class="replaceable"><code>column_name</code></em></span></dt><dd><p>
248 The name of a specific column to analyze. Defaults to all columns.
249 If a column list is specified, <code class="literal">ANALYZE</code> must also be
251 </p></dd></dl></div></div><div class="refsect1" id="id-1.9.3.184.7"><h2>Outputs</h2><p>
252 When <code class="literal">VERBOSE</code> is specified, <code class="command">VACUUM</code> emits
253 progress messages to indicate which table is currently being
254 processed. Various statistics about the tables are printed as well.
255 </p></div><div class="refsect1" id="id-1.9.3.184.8"><h2>Notes</h2><p>
256 To vacuum a table, one must ordinarily have the <code class="literal">MAINTAIN</code>
257 privilege on the table. However, database owners are allowed to
258 vacuum all tables in their databases, except shared catalogs.
259 <code class="command">VACUUM</code> will skip over any tables that the calling user
260 does not have permission to vacuum.
262 While <code class="command">VACUUM</code> is running, the <a class="xref" href="runtime-config-client.html#GUC-SEARCH-PATH">search_path</a> is temporarily changed to <code class="literal">pg_catalog,
265 <code class="command">VACUUM</code> cannot be executed inside a transaction block.
267 For tables with <acronym class="acronym">GIN</acronym> indexes, <code class="command">VACUUM</code> (in
268 any form) also completes any pending index insertions, by moving pending
269 index entries to the appropriate places in the main <acronym class="acronym">GIN</acronym> index
270 structure. See <a class="xref" href="gin.html#GIN-FAST-UPDATE" title="65.4.4.1. GIN Fast Update Technique">Section 65.4.4.1</a> for details.
272 We recommend that all databases be vacuumed regularly in
273 order to remove dead rows. <span class="productname">PostgreSQL</span> includes
274 an <span class="quote">“<span class="quote">autovacuum</span>”</span> facility which can automate routine vacuum
275 maintenance. For more information about automatic and manual vacuuming,
276 see <a class="xref" href="routine-vacuuming.html" title="24.1. Routine Vacuuming">Section 24.1</a>.
278 The <code class="option">FULL</code> option is not recommended for routine use,
279 but might be useful in special cases. An example is when you have deleted
280 or updated most of the rows in a table and would like the table to
281 physically shrink to occupy less disk space and allow faster table
282 scans. <code class="command">VACUUM FULL</code> will usually shrink the table
283 more than a plain <code class="command">VACUUM</code> would.
285 The <code class="option">PARALLEL</code> option is used only for vacuum purposes.
286 If this option is specified with the <code class="option">ANALYZE</code> option,
287 it does not affect <code class="option">ANALYZE</code>.
289 <code class="command">VACUUM</code> causes a substantial increase in I/O traffic,
290 which might cause poor performance for other active sessions. Therefore,
291 it is sometimes advisable to use the cost-based vacuum delay feature. For
292 parallel vacuum, each worker sleeps in proportion to the work done by that
293 worker. See <a class="xref" href="runtime-config-vacuum.html#RUNTIME-CONFIG-RESOURCE-VACUUM-COST" title="19.10.2. Cost-based Vacuum Delay">Section 19.10.2</a> for
296 Each backend running <code class="command">VACUUM</code> without the
297 <code class="literal">FULL</code> option will report its progress in the
298 <code class="structname">pg_stat_progress_vacuum</code> view. Backends running
299 <code class="command">VACUUM FULL</code> will instead report their progress in the
300 <code class="structname">pg_stat_progress_cluster</code> view. See
301 <a class="xref" href="progress-reporting.html#VACUUM-PROGRESS-REPORTING" title="27.4.5. VACUUM Progress Reporting">Section 27.4.5</a> and
302 <a class="xref" href="progress-reporting.html#CLUSTER-PROGRESS-REPORTING" title="27.4.2. CLUSTER Progress Reporting">Section 27.4.2</a> for details.
303 </p></div><div class="refsect1" id="id-1.9.3.184.9"><h2>Examples</h2><p>
304 To clean a single table <code class="literal">onek</code>, analyze it for
305 the optimizer and print a detailed vacuum activity report:
307 </p><pre class="programlisting">
308 VACUUM (VERBOSE, ANALYZE) onek;
309 </pre></div><div class="refsect1" id="id-1.9.3.184.10"><h2>Compatibility</h2><p>
310 There is no <code class="command">VACUUM</code> statement in the SQL standard.
312 The following syntax was used before <span class="productname">PostgreSQL</span>
313 version 9.0 and is still supported:
314 </p><pre class="synopsis">
315 VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] [ ANALYZE ] [ <em class="replaceable"><code>table_and_columns</code></em> [, ...] ]
317 Note that in this syntax, the options must be specified in exactly the order
319 </p></div><div class="refsect1" id="id-1.9.3.184.11"><h2>See Also</h2><span class="simplelist"><a class="xref" href="app-vacuumdb.html" title="vacuumdb"><span class="refentrytitle"><span class="application">vacuumdb</span></span></a>, <a class="xref" href="runtime-config-vacuum.html#RUNTIME-CONFIG-RESOURCE-VACUUM-COST" title="19.10.2. Cost-based Vacuum Delay">Section 19.10.2</a>, <a class="xref" href="routine-vacuuming.html#AUTOVACUUM" title="24.1.6. The Autovacuum Daemon">Section 24.1.6</a>, <a class="xref" href="progress-reporting.html#VACUUM-PROGRESS-REPORTING" title="27.4.5. VACUUM Progress Reporting">Section 27.4.5</a>, <a class="xref" href="progress-reporting.html#CLUSTER-PROGRESS-REPORTING" title="27.4.2. CLUSTER Progress Reporting">Section 27.4.2</a></span></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="sql-update.html" title="UPDATE">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="sql-commands.html" title="SQL Commands">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="sql-values.html" title="VALUES">Next</a></td></tr><tr><td width="40%" align="left" valign="top">UPDATE </td><td width="20%" align="center"><a accesskey="h" href="index.html" title="PostgreSQL 18.0 Documentation">Home</a></td><td width="40%" align="right" valign="top"> VALUES</td></tr></table></div></body></html>
begriffs.com / projects / ai-pg / blob