Submit
Path:
~
/
/
opt
/
alt
/
postgresql11
/
usr
/
share
/
doc
/
alt-postgresql11-9.2.24
/
html
/
File Content:
routine-vacuuming.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML ><HEAD ><TITLE >Routine Vacuuming</TITLE ><META NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK REV="MADE" HREF="mailto:pgsql-docs@postgresql.org"><LINK REL="HOME" TITLE="PostgreSQL 9.2.24 Documentation" HREF="index.html"><LINK REL="UP" TITLE="Routine Database Maintenance Tasks" HREF="maintenance.html"><LINK REL="PREVIOUS" TITLE="Routine Database Maintenance Tasks" HREF="maintenance.html"><LINK REL="NEXT" TITLE="Routine Reindexing" HREF="routine-reindex.html"><LINK REL="STYLESHEET" TYPE="text/css" HREF="stylesheet.css"><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1"><META NAME="creation" CONTENT="2017-11-06T22:43:11"></HEAD ><BODY CLASS="SECT1" ><DIV CLASS="NAVHEADER" ><TABLE SUMMARY="Header navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TH COLSPAN="5" ALIGN="center" VALIGN="bottom" ><A HREF="index.html" >PostgreSQL 9.2.24 Documentation</A ></TH ></TR ><TR ><TD WIDTH="10%" ALIGN="left" VALIGN="top" ><A TITLE="Routine Database Maintenance Tasks" HREF="maintenance.html" ACCESSKEY="P" >Prev</A ></TD ><TD WIDTH="10%" ALIGN="left" VALIGN="top" ><A HREF="maintenance.html" ACCESSKEY="U" >Up</A ></TD ><TD WIDTH="60%" ALIGN="center" VALIGN="bottom" >Chapter 23. Routine Database Maintenance Tasks</TD ><TD WIDTH="20%" ALIGN="right" VALIGN="top" ><A TITLE="Routine Reindexing" HREF="routine-reindex.html" ACCESSKEY="N" >Next</A ></TD ></TR ></TABLE ><HR ALIGN="LEFT" WIDTH="100%"></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A NAME="ROUTINE-VACUUMING" >23.1. Routine Vacuuming</A ></H1 ><P > <SPAN CLASS="PRODUCTNAME" >PostgreSQL</SPAN > databases require periodic maintenance known as <I CLASS="FIRSTTERM" >vacuuming</I >. For many installations, it is sufficient to let vacuuming be performed by the <I CLASS="FIRSTTERM" >autovacuum daemon</I >, which is described in <A HREF="routine-vacuuming.html#AUTOVACUUM" >Section 23.1.6</A >. You might need to adjust the autovacuuming parameters described there to obtain best results for your situation. Some database administrators will want to supplement or replace the daemon's activities with manually-managed <TT CLASS="COMMAND" >VACUUM</TT > commands, which typically are executed according to a schedule by <SPAN CLASS="APPLICATION" >cron</SPAN > or <SPAN CLASS="APPLICATION" >Task Scheduler</SPAN > scripts. To set up manually-managed vacuuming properly, it is essential to understand the issues discussed in the next few subsections. Administrators who rely on autovacuuming may still wish to skim this material to help them understand and adjust autovacuuming. </P ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A NAME="VACUUM-BASICS" >23.1.1. Vacuuming Basics</A ></H2 ><P > <SPAN CLASS="PRODUCTNAME" >PostgreSQL</SPAN >'s <A HREF="sql-vacuum.html" >VACUUM</A > command has to process each table on a regular basis for several reasons: <P ></P ></P><OL TYPE="1" ><LI ><P >To recover or reuse disk space occupied by updated or deleted rows.</P ></LI ><LI ><P >To update data statistics used by the <SPAN CLASS="PRODUCTNAME" >PostgreSQL</SPAN > query planner.</P ></LI ><LI ><P >To update the visibility map, which speeds up index-only scans.</P ></LI ><LI ><P >To protect against loss of very old data due to <I CLASS="FIRSTTERM" >transaction ID wraparound</I >.</P ></LI ></OL ><P> Each of these reasons dictates performing <TT CLASS="COMMAND" >VACUUM</TT > operations of varying frequency and scope, as explained in the following subsections. </P ><P > There are two variants of <TT CLASS="COMMAND" >VACUUM</TT >: standard <TT CLASS="COMMAND" >VACUUM</TT > and <TT CLASS="COMMAND" >VACUUM FULL</TT >. <TT CLASS="COMMAND" >VACUUM FULL</TT > can reclaim more disk space but runs much more slowly. Also, the standard form of <TT CLASS="COMMAND" >VACUUM</TT > can run in parallel with production database operations. (Commands such as <TT CLASS="COMMAND" >SELECT</TT >, <TT CLASS="COMMAND" >INSERT</TT >, <TT CLASS="COMMAND" >UPDATE</TT >, and <TT CLASS="COMMAND" >DELETE</TT > will continue to function normally, though you will not be able to modify the definition of a table with commands such as <TT CLASS="COMMAND" >ALTER TABLE</TT > while it is being vacuumed.) <TT CLASS="COMMAND" >VACUUM FULL</TT > requires exclusive lock on the table it is working on, and therefore cannot be done in parallel with other use of the table. Generally, therefore, administrators should strive to use standard <TT CLASS="COMMAND" >VACUUM</TT > and avoid <TT CLASS="COMMAND" >VACUUM FULL</TT >. </P ><P > <TT CLASS="COMMAND" >VACUUM</TT > creates a substantial amount of I/O traffic, which can cause poor performance for other active sessions. There are configuration parameters that can be adjusted to reduce the performance impact of background vacuuming — see <A HREF="runtime-config-resource.html#RUNTIME-CONFIG-RESOURCE-VACUUM-COST" >Section 18.4.4</A >. </P ></DIV ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A NAME="VACUUM-FOR-SPACE-RECOVERY" >23.1.2. Recovering Disk Space</A ></H2 ><P > In <SPAN CLASS="PRODUCTNAME" >PostgreSQL</SPAN >, an <TT CLASS="COMMAND" >UPDATE</TT > or <TT CLASS="COMMAND" >DELETE</TT > of a row does not immediately remove the old version of the row. This approach is necessary to gain the benefits of multiversion concurrency control (<ACRONYM CLASS="ACRONYM" >MVCC</ACRONYM >, see <A HREF="mvcc.html" >Chapter 13</A >): the row version must not be deleted while it is still potentially visible to other transactions. But eventually, an outdated or deleted row version is no longer of interest to any transaction. The space it occupies must then be reclaimed for reuse by new rows, to avoid unbounded growth of disk space requirements. This is done by running <TT CLASS="COMMAND" >VACUUM</TT >. </P ><P > The standard form of <TT CLASS="COMMAND" >VACUUM</TT > removes dead row versions in tables and indexes and marks the space available for future reuse. However, it will not return the space to the operating system, except in the special case where one or more pages at the end of a table become entirely free and an exclusive table lock can be easily obtained. In contrast, <TT CLASS="COMMAND" >VACUUM FULL</TT > actively compacts tables by writing a complete new version of the table file with no dead space. This minimizes the size of the table, but can take a long time. It also requires extra disk space for the new copy of the table, until the operation completes. </P ><P > The usual goal of routine vacuuming is to do standard <TT CLASS="COMMAND" >VACUUM</TT >s often enough to avoid needing <TT CLASS="COMMAND" >VACUUM FULL</TT >. The autovacuum daemon attempts to work this way, and in fact will never issue <TT CLASS="COMMAND" >VACUUM FULL</TT >. In this approach, the idea is not to keep tables at their minimum size, but to maintain steady-state usage of disk space: each table occupies space equivalent to its minimum size plus however much space gets used up between vacuumings. Although <TT CLASS="COMMAND" >VACUUM FULL</TT > can be used to shrink a table back to its minimum size and return the disk space to the operating system, there is not much point in this if the table will just grow again in the future. Thus, moderately-frequent standard <TT CLASS="COMMAND" >VACUUM</TT > runs are a better approach than infrequent <TT CLASS="COMMAND" >VACUUM FULL</TT > runs for maintaining heavily-updated tables. </P ><P > Some administrators prefer to schedule vacuuming themselves, for example doing all the work at night when load is low. The difficulty with doing vacuuming according to a fixed schedule is that if a table has an unexpected spike in update activity, it may get bloated to the point that <TT CLASS="COMMAND" >VACUUM FULL</TT > is really necessary to reclaim space. Using the autovacuum daemon alleviates this problem, since the daemon schedules vacuuming dynamically in response to update activity. It is unwise to disable the daemon completely unless you have an extremely predictable workload. One possible compromise is to set the daemon's parameters so that it will only react to unusually heavy update activity, thus keeping things from getting out of hand, while scheduled <TT CLASS="COMMAND" >VACUUM</TT >s are expected to do the bulk of the work when the load is typical. </P ><P > For those not using autovacuum, a typical approach is to schedule a database-wide <TT CLASS="COMMAND" >VACUUM</TT > once a day during a low-usage period, supplemented by more frequent vacuuming of heavily-updated tables as necessary. (Some installations with extremely high update rates vacuum their busiest tables as often as once every few minutes.) If you have multiple databases in a cluster, don't forget to <TT CLASS="COMMAND" >VACUUM</TT > each one; the program <A HREF="app-vacuumdb.html" ><SPAN CLASS="APPLICATION" >vacuumdb</SPAN ></A > might be helpful. </P ><DIV CLASS="TIP" ><BLOCKQUOTE CLASS="TIP" ><P ><B >Tip: </B > Plain <TT CLASS="COMMAND" >VACUUM</TT > may not be satisfactory when a table contains large numbers of dead row versions as a result of massive update or delete activity. If you have such a table and you need to reclaim the excess disk space it occupies, you will need to use <TT CLASS="COMMAND" >VACUUM FULL</TT >, or alternatively <A HREF="sql-cluster.html" >CLUSTER</A > or one of the table-rewriting variants of <A HREF="sql-altertable.html" >ALTER TABLE</A >. These commands rewrite an entire new copy of the table and build new indexes for it. All these options require exclusive lock. Note that they also temporarily use extra disk space approximately equal to the size of the table, since the old copies of the table and indexes can't be released until the new ones are complete. </P ></BLOCKQUOTE ></DIV ><DIV CLASS="TIP" ><BLOCKQUOTE CLASS="TIP" ><P ><B >Tip: </B > If you have a table whose entire contents are deleted on a periodic basis, consider doing it with <A HREF="sql-truncate.html" >TRUNCATE</A > rather than using <TT CLASS="COMMAND" >DELETE</TT > followed by <TT CLASS="COMMAND" >VACUUM</TT >. <TT CLASS="COMMAND" >TRUNCATE</TT > removes the entire content of the table immediately, without requiring a subsequent <TT CLASS="COMMAND" >VACUUM</TT > or <TT CLASS="COMMAND" >VACUUM FULL</TT > to reclaim the now-unused disk space. The disadvantage is that strict MVCC semantics are violated. </P ></BLOCKQUOTE ></DIV ></DIV ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A NAME="VACUUM-FOR-STATISTICS" >23.1.3. Updating Planner Statistics</A ></H2 ><P > The <SPAN CLASS="PRODUCTNAME" >PostgreSQL</SPAN > query planner relies on statistical information about the contents of tables in order to generate good plans for queries. These statistics are gathered by the <A HREF="sql-analyze.html" >ANALYZE</A > command, which can be invoked by itself or as an optional step in <TT CLASS="COMMAND" >VACUUM</TT >. It is important to have reasonably accurate statistics, otherwise poor choices of plans might degrade database performance. </P ><P > The autovacuum daemon, if enabled, will automatically issue <TT CLASS="COMMAND" >ANALYZE</TT > commands whenever the content of a table has changed sufficiently. However, administrators might prefer to rely on manually-scheduled <TT CLASS="COMMAND" >ANALYZE</TT > operations, particularly if it is known that update activity on a table will not affect the statistics of <SPAN CLASS="QUOTE" >"interesting"</SPAN > columns. The daemon schedules <TT CLASS="COMMAND" >ANALYZE</TT > strictly as a function of the number of rows inserted or updated; it has no knowledge of whether that will lead to meaningful statistical changes. </P ><P > As with vacuuming for space recovery, frequent updates of statistics are more useful for heavily-updated tables than for seldom-updated ones. But even for a heavily-updated table, there might be no need for statistics updates if the statistical distribution of the data is not changing much. A simple rule of thumb is to think about how much the minimum and maximum values of the columns in the table change. For example, a <TT CLASS="TYPE" >timestamp</TT > column that contains the time of row update will have a constantly-increasing maximum value as rows are added and updated; such a column will probably need more frequent statistics updates than, say, a column containing URLs for pages accessed on a website. The URL column might receive changes just as often, but the statistical distribution of its values probably changes relatively slowly. </P ><P > It is possible to run <TT CLASS="COMMAND" >ANALYZE</TT > on specific tables and even just specific columns of a table, so the flexibility exists to update some statistics more frequently than others if your application requires it. In practice, however, it is usually best to just analyze the entire database, because it is a fast operation. <TT CLASS="COMMAND" >ANALYZE</TT > uses a statistically random sampling of the rows of a table rather than reading every single row. </P ><DIV CLASS="TIP" ><BLOCKQUOTE CLASS="TIP" ><P ><B >Tip: </B > Although per-column tweaking of <TT CLASS="COMMAND" >ANALYZE</TT > frequency might not be very productive, you might find it worthwhile to do per-column adjustment of the level of detail of the statistics collected by <TT CLASS="COMMAND" >ANALYZE</TT >. Columns that are heavily used in <TT CLASS="LITERAL" >WHERE</TT > clauses and have highly irregular data distributions might require a finer-grain data histogram than other columns. See <TT CLASS="COMMAND" >ALTER TABLE SET STATISTICS</TT >, or change the database-wide default using the <A HREF="runtime-config-query.html#GUC-DEFAULT-STATISTICS-TARGET" >default_statistics_target</A > configuration parameter. </P ><P > Also, by default there is limited information available about the selectivity of functions. However, if you create an expression index that uses a function call, useful statistics will be gathered about the function, which can greatly improve query plans that use the expression index. </P ></BLOCKQUOTE ></DIV ><DIV CLASS="TIP" ><BLOCKQUOTE CLASS="TIP" ><P ><B >Tip: </B > The autovacuum daemon does not issue <TT CLASS="COMMAND" >ANALYZE</TT > commands for foreign tables, since it has no means of determining how often that might be useful. If your queries require statistics on foreign tables for proper planning, it's a good idea to run manually-managed <TT CLASS="COMMAND" >ANALYZE</TT > commands on those tables on a suitable schedule. </P ></BLOCKQUOTE ></DIV ></DIV ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A NAME="VACUUM-FOR-VISIBILITY-MAP" >23.1.4. Updating The Visibility Map</A ></H2 ><P > Vacuum maintains a <A HREF="storage-vm.html" >visibility map</A > for each table to keep track of which pages contain only tuples that are known to be visible to all active transactions (and all future transactions, until the page is again modified). This has two purposes. First, vacuum itself can skip such pages on the next run, since there is nothing to clean up. </P ><P > Second, it allows <SPAN CLASS="PRODUCTNAME" >PostgreSQL</SPAN > to answer some queries using only the index, without reference to the underlying table. Since <SPAN CLASS="PRODUCTNAME" >PostgreSQL</SPAN > indexes don't contain tuple visibility information, a normal index scan fetches the heap tuple for each matching index entry, to check whether it should be seen by the current transaction. An <I CLASS="FIRSTTERM" >index-only scan</I >, on the other hand, checks the visibility map first. If it's known that all tuples on the page are visible, the heap fetch can be skipped. This is most noticeable on large data sets where the visibility map can prevent disk accesses. The visibility map is vastly smaller than the heap, so it can easily be cached even when the heap is very large. </P ></DIV ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A NAME="VACUUM-FOR-WRAPAROUND" >23.1.5. Preventing Transaction ID Wraparound Failures</A ></H2 ><P > <SPAN CLASS="PRODUCTNAME" >PostgreSQL</SPAN >'s MVCC transaction semantics depend on being able to compare transaction ID (<ACRONYM CLASS="ACRONYM" >XID</ACRONYM >) numbers: a row version with an insertion XID greater than the current transaction's XID is <SPAN CLASS="QUOTE" >"in the future"</SPAN > and should not be visible to the current transaction. But since transaction IDs have limited size (32 bits) a cluster that runs for a long time (more than 4 billion transactions) would suffer <I CLASS="FIRSTTERM" >transaction ID wraparound</I >: the XID counter wraps around to zero, and all of a sudden transactions that were in the past appear to be in the future — which means their output become invisible. In short, catastrophic data loss. (Actually the data is still there, but that's cold comfort if you cannot get at it.) To avoid this, it is necessary to vacuum every table in every database at least once every two billion transactions. </P ><P > The reason that periodic vacuuming solves the problem is that <SPAN CLASS="PRODUCTNAME" >PostgreSQL</SPAN > reserves a special XID as <TT CLASS="LITERAL" >FrozenXID</TT >. This XID does not follow the normal XID comparison rules and is always considered older than every normal XID. Normal XIDs are compared using modulo-2<SUP >32</SUP > arithmetic. This means that for every normal XID, there are two billion XIDs that are <SPAN CLASS="QUOTE" >"older"</SPAN > and two billion that are <SPAN CLASS="QUOTE" >"newer"</SPAN >; another way to say it is that the normal XID space is circular with no endpoint. Therefore, once a row version has been created with a particular normal XID, the row version will appear to be <SPAN CLASS="QUOTE" >"in the past"</SPAN > for the next two billion transactions, no matter which normal XID we are talking about. If the row version still exists after more than two billion transactions, it will suddenly appear to be in the future. To prevent this, old row versions must be reassigned the XID <TT CLASS="LITERAL" >FrozenXID</TT > sometime before they reach the two-billion-transactions-old mark. Once they are assigned this special XID, they will appear to be <SPAN CLASS="QUOTE" >"in the past"</SPAN > to all normal transactions regardless of wraparound issues, and so such row versions will be valid until deleted, no matter how long that is. This reassignment of old XIDs is handled by <TT CLASS="COMMAND" >VACUUM</TT >. </P ><P > <A HREF="runtime-config-client.html#GUC-VACUUM-FREEZE-MIN-AGE" >vacuum_freeze_min_age</A > controls how old an XID value has to be before it's replaced with <TT CLASS="LITERAL" >FrozenXID</TT >. Larger values of this setting preserve transactional information longer, while smaller values increase the number of transactions that can elapse before the table must be vacuumed again. </P ><P > <TT CLASS="COMMAND" >VACUUM</TT > normally skips pages that don't have any dead row versions, but those pages might still have row versions with old XID values. To ensure all old XIDs have been replaced by <TT CLASS="LITERAL" >FrozenXID</TT >, a scan of the whole table is needed. <A HREF="runtime-config-client.html#GUC-VACUUM-FREEZE-TABLE-AGE" >vacuum_freeze_table_age</A > controls when <TT CLASS="COMMAND" >VACUUM</TT > does that: a whole table sweep is forced if the table hasn't been fully scanned for <TT CLASS="VARNAME" >vacuum_freeze_table_age</TT > minus <TT CLASS="VARNAME" >vacuum_freeze_min_age</TT > transactions. Setting it to 0 forces <TT CLASS="COMMAND" >VACUUM</TT > to always scan all pages, effectively ignoring the visibility map. </P ><P > The maximum time that a table can go unvacuumed is two billion transactions minus the <TT CLASS="VARNAME" >vacuum_freeze_min_age</TT > value at the time <TT CLASS="COMMAND" >VACUUM</TT > last scanned the whole table. If it were to go unvacuumed for longer than that, data loss could result. To ensure that this does not happen, autovacuum is invoked on any table that might contain XIDs older than the age specified by the configuration parameter <A HREF="runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE" >autovacuum_freeze_max_age</A >. (This will happen even if autovacuum is disabled.) </P ><P > This implies that if a table is not otherwise vacuumed, autovacuum will be invoked on it approximately once every <TT CLASS="VARNAME" >autovacuum_freeze_max_age</TT > minus <TT CLASS="VARNAME" >vacuum_freeze_min_age</TT > transactions. For tables that are regularly vacuumed for space reclamation purposes, this is of little importance. However, for static tables (including tables that receive inserts, but no updates or deletes), there is no need to vacuum for space reclamation, so it can be useful to try to maximize the interval between forced autovacuums on very large static tables. Obviously one can do this either by increasing <TT CLASS="VARNAME" >autovacuum_freeze_max_age</TT > or decreasing <TT CLASS="VARNAME" >vacuum_freeze_min_age</TT >. </P ><P > The effective maximum for <TT CLASS="VARNAME" >vacuum_freeze_table_age</TT > is 0.95 * <TT CLASS="VARNAME" >autovacuum_freeze_max_age</TT >; a setting higher than that will be capped to the maximum. A value higher than <TT CLASS="VARNAME" >autovacuum_freeze_max_age</TT > wouldn't make sense because an anti-wraparound autovacuum would be triggered at that point anyway, and the 0.95 multiplier leaves some breathing room to run a manual <TT CLASS="COMMAND" >VACUUM</TT > before that happens. As a rule of thumb, <TT CLASS="COMMAND" >vacuum_freeze_table_age</TT > should be set to a value somewhat below <TT CLASS="VARNAME" >autovacuum_freeze_max_age</TT >, leaving enough gap so that a regularly scheduled <TT CLASS="COMMAND" >VACUUM</TT > or an autovacuum triggered by normal delete and update activity is run in that window. Setting it too close could lead to anti-wraparound autovacuums, even though the table was recently vacuumed to reclaim space, whereas lower values lead to more frequent whole-table scans. </P ><P > The sole disadvantage of increasing <TT CLASS="VARNAME" >autovacuum_freeze_max_age</TT > (and <TT CLASS="VARNAME" >vacuum_freeze_table_age</TT > along with it) is that the <TT CLASS="FILENAME" >pg_clog</TT > subdirectory of the database cluster will take more space, because it must store the commit status of all transactions back to the <TT CLASS="VARNAME" >autovacuum_freeze_max_age</TT > horizon. The commit status uses two bits per transaction, so if <TT CLASS="VARNAME" >autovacuum_freeze_max_age</TT > is set to its maximum allowed value of two billion, <TT CLASS="FILENAME" >pg_clog</TT > can be expected to grow to about half a gigabyte. If this is trivial compared to your total database size, setting <TT CLASS="VARNAME" >autovacuum_freeze_max_age</TT > to its maximum allowed value is recommended. Otherwise, set it depending on what you are willing to allow for <TT CLASS="FILENAME" >pg_clog</TT > storage. (The default, 200 million transactions, translates to about 50MB of <TT CLASS="FILENAME" >pg_clog</TT > storage.) </P ><P > One disadvantage of decreasing <TT CLASS="VARNAME" >vacuum_freeze_min_age</TT > is that it might cause <TT CLASS="COMMAND" >VACUUM</TT > to do useless work: changing a table row's XID to <TT CLASS="LITERAL" >FrozenXID</TT > is a waste of time if the row is modified soon thereafter (causing it to acquire a new XID). So the setting should be large enough that rows are not frozen until they are unlikely to change any more. Another disadvantage of decreasing this setting is that details about exactly which transaction inserted or modified a row will be lost sooner. This information sometimes comes in handy, particularly when trying to analyze what went wrong after a database failure. For these two reasons, decreasing this setting is not recommended except for completely static tables. </P ><P > To track the age of the oldest XIDs in a database, <TT CLASS="COMMAND" >VACUUM</TT > stores XID statistics in the system tables <TT CLASS="STRUCTNAME" >pg_class</TT > and <TT CLASS="STRUCTNAME" >pg_database</TT >. In particular, the <TT CLASS="STRUCTFIELD" >relfrozenxid</TT > column of a table's <TT CLASS="STRUCTNAME" >pg_class</TT > row contains the freeze cutoff XID that was used by the last whole-table <TT CLASS="COMMAND" >VACUUM</TT > for that table. All normal XIDs older than this cutoff XID are guaranteed to have been replaced by <TT CLASS="LITERAL" >FrozenXID</TT > within the table. Similarly, the <TT CLASS="STRUCTFIELD" >datfrozenxid</TT > column of a database's <TT CLASS="STRUCTNAME" >pg_database</TT > row is a lower bound on the normal XIDs appearing in that database — it is just the minimum of the per-table <TT CLASS="STRUCTFIELD" >relfrozenxid</TT > values within the database. A convenient way to examine this information is to execute queries such as: </P><PRE CLASS="PROGRAMLISTING" >SELECT c.oid::regclass as table_name, greatest(age(c.relfrozenxid),age(t.relfrozenxid)) as age FROM pg_class c LEFT JOIN pg_class t ON c.reltoastrelid = t.oid WHERE c.relkind = 'r'; SELECT datname, age(datfrozenxid) FROM pg_database;</PRE ><P> The <TT CLASS="LITERAL" >age</TT > column measures the number of transactions from the cutoff XID to the current transaction's XID. </P ><P > <TT CLASS="COMMAND" >VACUUM</TT > normally only scans pages that have been modified since the last vacuum, but <TT CLASS="STRUCTFIELD" >relfrozenxid</TT > can only be advanced when the whole table is scanned. The whole table is scanned when <TT CLASS="STRUCTFIELD" >relfrozenxid</TT > is more than <TT CLASS="VARNAME" >vacuum_freeze_table_age</TT > transactions old, when <TT CLASS="COMMAND" >VACUUM</TT >'s <TT CLASS="LITERAL" >FREEZE</TT > option is used, or when all pages happen to require vacuuming to remove dead row versions. When <TT CLASS="COMMAND" >VACUUM</TT > scans the whole table, after it's finished <TT CLASS="LITERAL" >age(relfrozenxid)</TT > should be a little more than the <TT CLASS="VARNAME" >vacuum_freeze_min_age</TT > setting that was used (more by the number of transactions started since the <TT CLASS="COMMAND" >VACUUM</TT > started). If no whole-table-scanning <TT CLASS="COMMAND" >VACUUM</TT > is issued on the table until <TT CLASS="VARNAME" >autovacuum_freeze_max_age</TT > is reached, an autovacuum will soon be forced for the table. </P ><P > If for some reason autovacuum fails to clear old XIDs from a table, the system will begin to emit warning messages like this when the database's oldest XIDs reach ten million transactions from the wraparound point: </P><PRE CLASS="PROGRAMLISTING" >WARNING: database "mydb" must be vacuumed within 177009986 transactions HINT: To avoid a database shutdown, execute a database-wide VACUUM in "mydb".</PRE ><P> (A manual <TT CLASS="COMMAND" >VACUUM</TT > should fix the problem, as suggested by the hint; but note that the <TT CLASS="COMMAND" >VACUUM</TT > must be performed by a superuser, else it will fail to process system catalogs and thus not be able to advance the database's <TT CLASS="STRUCTFIELD" >datfrozenxid</TT >.) If these warnings are ignored, the system will shut down and refuse to start any new transactions once there are fewer than 1 million transactions left until wraparound: </P><PRE CLASS="PROGRAMLISTING" >ERROR: database is not accepting commands to avoid wraparound data loss in database "mydb" HINT: Stop the postmaster and use a standalone backend to VACUUM in "mydb".</PRE ><P> The 1-million-transaction safety margin exists to let the administrator recover without data loss, by manually executing the required <TT CLASS="COMMAND" >VACUUM</TT > commands. However, since the system will not execute commands once it has gone into the safety shutdown mode, the only way to do this is to stop the server and use a single-user backend to execute <TT CLASS="COMMAND" >VACUUM</TT >. The shutdown mode is not enforced by a single-user backend. See the <A HREF="app-postgres.html" ><SPAN CLASS="APPLICATION" >postgres</SPAN ></A > reference page for details about using a single-user backend. </P ></DIV ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A NAME="AUTOVACUUM" >23.1.6. The Autovacuum Daemon</A ></H2 ><P > <SPAN CLASS="PRODUCTNAME" >PostgreSQL</SPAN > has an optional but highly recommended feature called <I CLASS="FIRSTTERM" >autovacuum</I >, whose purpose is to automate the execution of <TT CLASS="COMMAND" >VACUUM</TT > and <TT CLASS="COMMAND" >ANALYZE </TT > commands. When enabled, autovacuum checks for tables that have had a large number of inserted, updated or deleted tuples. These checks use the statistics collection facility; therefore, autovacuum cannot be used unless <A HREF="runtime-config-statistics.html#GUC-TRACK-COUNTS" >track_counts</A > is set to <TT CLASS="LITERAL" >true</TT >. In the default configuration, autovacuuming is enabled and the related configuration parameters are appropriately set. </P ><P > The <SPAN CLASS="QUOTE" >"autovacuum daemon"</SPAN > actually consists of multiple processes. There is a persistent daemon process, called the <I CLASS="FIRSTTERM" >autovacuum launcher</I >, which is in charge of starting <I CLASS="FIRSTTERM" >autovacuum worker</I > processes for all databases. The launcher will distribute the work across time, attempting to start one worker within each database every <A HREF="runtime-config-autovacuum.html#GUC-AUTOVACUUM-NAPTIME" >autovacuum_naptime</A > seconds. (Therefore, if the installation has <TT CLASS="REPLACEABLE" ><I >N</I ></TT > databases, a new worker will be launched every <TT CLASS="VARNAME" >autovacuum_naptime</TT >/<TT CLASS="REPLACEABLE" ><I >N</I ></TT > seconds.) A maximum of <A HREF="runtime-config-autovacuum.html#GUC-AUTOVACUUM-MAX-WORKERS" >autovacuum_max_workers</A > worker processes are allowed to run at the same time. If there are more than <TT CLASS="VARNAME" >autovacuum_max_workers</TT > databases to be processed, the next database will be processed as soon as the first worker finishes. Each worker process will check each table within its database and execute <TT CLASS="COMMAND" >VACUUM</TT > and/or <TT CLASS="COMMAND" >ANALYZE</TT > as needed. </P ><P > If several large tables all become eligible for vacuuming in a short amount of time, all autovacuum workers might become occupied with vacuuming those tables for a long period. This would result in other tables and databases not being vacuumed until a worker became available. There is no limit on how many workers might be in a single database, but workers do try to avoid repeating work that has already been done by other workers. Note that the number of running workers does not count towards <A HREF="runtime-config-connection.html#GUC-MAX-CONNECTIONS" >max_connections</A > or <A HREF="runtime-config-connection.html#GUC-SUPERUSER-RESERVED-CONNECTIONS" >superuser_reserved_connections</A > limits. </P ><P > Tables whose <TT CLASS="STRUCTFIELD" >relfrozenxid</TT > value is more than <A HREF="runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE" >autovacuum_freeze_max_age</A > transactions old are always vacuumed (this also applies to those tables whose freeze max age has been modified via storage parameters; see below). Otherwise, if the number of tuples obsoleted since the last <TT CLASS="COMMAND" >VACUUM</TT > exceeds the <SPAN CLASS="QUOTE" >"vacuum threshold"</SPAN >, the table is vacuumed. The vacuum threshold is defined as: </P><PRE CLASS="PROGRAMLISTING" >vacuum threshold = vacuum base threshold + vacuum scale factor * number of tuples</PRE ><P> where the vacuum base threshold is <A HREF="runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-THRESHOLD" >autovacuum_vacuum_threshold</A >, the vacuum scale factor is <A HREF="runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-SCALE-FACTOR" >autovacuum_vacuum_scale_factor</A >, and the number of tuples is <TT CLASS="STRUCTNAME" >pg_class</TT >.<TT CLASS="STRUCTFIELD" >reltuples</TT >. The number of obsolete tuples is obtained from the statistics collector; it is a semi-accurate count updated by each <TT CLASS="COMMAND" >UPDATE</TT > and <TT CLASS="COMMAND" >DELETE</TT > operation. (It is only semi-accurate because some information might be lost under heavy load.) If the <TT CLASS="STRUCTFIELD" >relfrozenxid</TT > value of the table is more than <TT CLASS="VARNAME" >vacuum_freeze_table_age</TT > transactions old, the whole table is scanned to freeze old tuples and advance <TT CLASS="STRUCTFIELD" >relfrozenxid</TT >, otherwise only pages that have been modified since the last vacuum are scanned. </P ><P > For analyze, a similar condition is used: the threshold, defined as: </P><PRE CLASS="PROGRAMLISTING" >analyze threshold = analyze base threshold + analyze scale factor * number of tuples</PRE ><P> is compared to the total number of tuples inserted, updated, or deleted since the last <TT CLASS="COMMAND" >ANALYZE</TT >. </P ><P > Temporary tables cannot be accessed by autovacuum. Therefore, appropriate vacuum and analyze operations should be performed via session SQL commands. </P ><P > The default thresholds and scale factors are taken from <TT CLASS="FILENAME" >postgresql.conf</TT >, but it is possible to override them on a table-by-table basis; see <A HREF="sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS" ><I >Storage Parameters</I ></A > for more information. If a setting has been changed via storage parameters, that value is used; otherwise the global settings are used. See <A HREF="runtime-config-autovacuum.html" >Section 18.10</A > for more details on the global settings. </P ><P > Besides the base threshold values and scale factors, there are six more autovacuum parameters that can be set for each table via storage parameters. The first parameter, <TT CLASS="LITERAL" >autovacuum_enabled</TT >, can be set to <TT CLASS="LITERAL" >false</TT > to instruct the autovacuum daemon to skip that particular table entirely. In this case autovacuum will only touch the table if it must do so to prevent transaction ID wraparound. Another two parameters, <TT CLASS="VARNAME" >autovacuum_vacuum_cost_delay</TT > and <TT CLASS="VARNAME" >autovacuum_vacuum_cost_limit</TT >, are used to set table-specific values for the cost-based vacuum delay feature (see <A HREF="runtime-config-resource.html#RUNTIME-CONFIG-RESOURCE-VACUUM-COST" >Section 18.4.4</A >). <TT CLASS="VARNAME" >autovacuum_freeze_min_age</TT >, <TT CLASS="VARNAME" >autovacuum_freeze_max_age</TT > and <TT CLASS="VARNAME" >autovacuum_freeze_table_age</TT > are used to set values for <A HREF="runtime-config-client.html#GUC-VACUUM-FREEZE-MIN-AGE" >vacuum_freeze_min_age</A >, <A HREF="runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE" >autovacuum_freeze_max_age</A > and <A HREF="runtime-config-client.html#GUC-VACUUM-FREEZE-TABLE-AGE" >vacuum_freeze_table_age</A > respectively. </P ><P > When multiple workers are running, the cost delay parameters are <SPAN CLASS="QUOTE" >"balanced"</SPAN > among all the running workers, so that the total I/O impact on the system is the same regardless of the number of workers actually running. However, any workers processing tables whose <TT CLASS="LITERAL" >autovacuum_vacuum_cost_delay</TT > or <TT CLASS="LITERAL" >autovacuum_vacuum_cost_limit</TT > have been set are not considered in the balancing algorithm. </P ></DIV ></DIV ><DIV CLASS="NAVFOOTER" ><HR ALIGN="LEFT" WIDTH="100%"><TABLE SUMMARY="Footer navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" ><A HREF="maintenance.html" ACCESSKEY="P" >Prev</A ></TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A HREF="index.html" ACCESSKEY="H" >Home</A ></TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" ><A HREF="routine-reindex.html" ACCESSKEY="N" >Next</A ></TD ></TR ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" >Routine Database Maintenance Tasks</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A HREF="maintenance.html" ACCESSKEY="U" >Up</A ></TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" >Routine Reindexing</TD ></TR ></TABLE ></DIV ></BODY ></HTML >
Submit
FILE
FOLDER
Name
Size
Permission
Action
LEGALNOTICE.html
2681 bytes
0644
acronyms.html
16284 bytes
0644
admin.html
12564 bytes
0644
adminpack.html
7889 bytes
0644
app-clusterdb.html
10602 bytes
0644
app-createdb.html
12856 bytes
0644
app-createlang.html
9907 bytes
0644
app-createuser.html
15640 bytes
0644
app-dropdb.html
9642 bytes
0644
app-droplang.html
9638 bytes
0644
app-dropuser.html
9596 bytes
0644
app-ecpg.html
8718 bytes
0644
app-initdb.html
15405 bytes
0644
app-pg-ctl.html
22459 bytes
0644
app-pg-dumpall.html
20706 bytes
0644
app-pgbasebackup.html
19833 bytes
0644
app-pgconfig.html
11093 bytes
0644
app-pgcontroldata.html
3979 bytes
0644
app-pgdump.html
43964 bytes
0644
app-pgreceivexlog.html
11057 bytes
0644
app-pgresetxlog.html
11566 bytes
0644
app-pgrestore.html
30269 bytes
0644
app-postgres.html
31828 bytes
0644
app-postmaster.html
3005 bytes
0644
app-psql.html
138871 bytes
0644
app-reindexdb.html
11281 bytes
0644
app-vacuumdb.html
12616 bytes
0644
appendixes.html
26329 bytes
0644
applevel-consistency.html
10315 bytes
0644
archive-recovery-settings.html
7338 bytes
0644
arrays.html
28079 bytes
0644
auth-delay.html
3780 bytes
0644
auth-methods.html
36202 bytes
0644
auth-pg-hba-conf.html
29759 bytes
0644
auth-username-maps.html
8597 bytes
0644
auto-explain.html
9887 bytes
0644
backup-dump.html
15927 bytes
0644
backup-file.html
7996 bytes
0644
backup.html
4485 bytes
0644
biblio.html
11549 bytes
0644
bki-commands.html
9646 bytes
0644
bki-example.html
3049 bytes
0644
bki-format.html
3463 bytes
0644
bki-structure.html
4320 bytes
0644
bki.html
4330 bytes
0644
bookindex.html
243165 bytes
0644
btree-gin.html
4600 bytes
0644
btree-gist.html
6884 bytes
0644
bug-reporting.html
18646 bytes
0644
catalog-pg-aggregate.html
5502 bytes
0644
catalog-pg-am.html
10547 bytes
0644
catalog-pg-amop.html
7593 bytes
0644
catalog-pg-amproc.html
4885 bytes
0644
catalog-pg-attrdef.html
4364 bytes
0644
catalog-pg-attribute.html
10287 bytes
0644
catalog-pg-auth-members.html
4255 bytes
0644
catalog-pg-authid.html
6815 bytes
0644
catalog-pg-cast.html
6955 bytes
0644
catalog-pg-class.html
12661 bytes
0644
catalog-pg-collation.html
5897 bytes
0644
catalog-pg-constraint.html
11579 bytes
0644
catalog-pg-conversion.html
4430 bytes
0644
catalog-pg-database.html
7027 bytes
0644
catalog-pg-db-role-setting.html
4068 bytes
0644
catalog-pg-default-acl.html
5267 bytes
0644
catalog-pg-depend.html
8635 bytes
0644
catalog-pg-description.html
4478 bytes
0644
catalog-pg-enum.html
4716 bytes
0644
catalog-pg-extension.html
5282 bytes
0644
catalog-pg-foreign-data-wrapper.html
4945 bytes
0644
catalog-pg-foreign-server.html
4688 bytes
0644
catalog-pg-foreign-table.html
4036 bytes
0644
catalog-pg-index.html
8868 bytes
0644
catalog-pg-inherits.html
3888 bytes
0644
catalog-pg-language.html
5952 bytes
0644
catalog-pg-largeobject-metadata.html
3630 bytes
0644
catalog-pg-largeobject.html
5154 bytes
0644
catalog-pg-namespace.html
3751 bytes
0644
catalog-pg-opclass.html
5863 bytes
0644
catalog-pg-operator.html
6645 bytes
0644
catalog-pg-opfamily.html
4811 bytes
0644
catalog-pg-pltemplate.html
5364 bytes
0644
catalog-pg-proc.html
13403 bytes
0644
catalog-pg-range.html
5182 bytes
0644
catalog-pg-rewrite.html
5391 bytes
0644
catalog-pg-seclabel.html
4515 bytes
0644
catalog-pg-shdepend.html
7043 bytes
0644
catalog-pg-shdescription.html
4247 bytes
0644
catalog-pg-shseclabel.html
4404 bytes
0644
catalog-pg-statistic.html
9538 bytes
0644
catalog-pg-tablespace.html
4158 bytes
0644
catalog-pg-trigger.html
8287 bytes
0644
catalog-pg-ts-config-map.html
4193 bytes
0644
catalog-pg-ts-config.html
4481 bytes
0644
catalog-pg-ts-dict.html
4716 bytes
0644
catalog-pg-ts-parser.html
5082 bytes
0644
catalog-pg-ts-template.html
4258 bytes
0644
catalog-pg-type.html
19905 bytes
0644
catalog-pg-user-mapping.html
3847 bytes
0644
catalogs-overview.html
10431 bytes
0644
catalogs.html
10387 bytes
0644
charset.html
4162 bytes
0644
chkpass.html
4391 bytes
0644
citext.html
11148 bytes
0644
client-authentication-problems.html
4224 bytes
0644
client-authentication.html
5914 bytes
0644
client-interfaces.html
13717 bytes
0644
collation.html
14222 bytes
0644
config-setting.html
11146 bytes
0644
connect-estab.html
4315 bytes
0644
continuous-archiving.html
49830 bytes
0644
contrib-dblink-build-sql-delete.html
5451 bytes
0644
contrib-dblink-build-sql-insert.html
6052 bytes
0644
contrib-dblink-build-sql-update.html
6281 bytes
0644
contrib-dblink-cancel-query.html
3820 bytes
0644
contrib-dblink-close.html
4650 bytes
0644
contrib-dblink-connect-u.html
4482 bytes
0644
contrib-dblink-connect.html
7325 bytes
0644
contrib-dblink-disconnect.html
3718 bytes
0644
contrib-dblink-error-message.html
3508 bytes
0644
contrib-dblink-exec.html
5466 bytes
0644
contrib-dblink-fetch.html
5979 bytes
0644
contrib-dblink-function.html
8630 bytes
0644
contrib-dblink-get-connections.html
3206 bytes
0644
contrib-dblink-get-notify.html
4168 bytes
0644
contrib-dblink-get-pkey.html
4498 bytes
0644
contrib-dblink-get-result.html
6959 bytes
0644
contrib-dblink-is-busy.html
3490 bytes
0644
contrib-dblink-open.html
5464 bytes
0644
contrib-dblink-send-query.html
4170 bytes
0644
contrib-prog-client.html
3434 bytes
0644
contrib-prog-server.html
3837 bytes
0644
contrib-prog.html
3320 bytes
0644
contrib-spi.html
11236 bytes
0644
contrib.html
8904 bytes
0644
creating-cluster.html
12465 bytes
0644
cube.html
15941 bytes
0644
database-roles.html
6092 bytes
0644
datatype-binary.html
12893 bytes
0644
datatype-bit.html
5096 bytes
0644
datatype-boolean.html
5267 bytes
0644
datatype-character.html
11893 bytes
0644
datatype-datetime.html
50763 bytes
0644
datatype-enum.html
6433 bytes
0644
datatype-geometric.html
12503 bytes
0644
datatype-json.html
3439 bytes
0644
datatype-money.html
5482 bytes
0644
datatype-net-types.html
10423 bytes
0644
datatype-numeric.html
22353 bytes
0644
datatype-oid.html
9686 bytes
0644
datatype-pseudo.html
7285 bytes
0644
datatype-textsearch.html
10033 bytes
0644
datatype-uuid.html
4560 bytes
0644
datatype-xml.html
11334 bytes
0644
datatype.html
16609 bytes
0644
datetime-appendix.html
3525 bytes
0644
datetime-config-files.html
8980 bytes
0644
datetime-input-rules.html
6763 bytes
0644
datetime-keywords.html
5096 bytes
0644
datetime-units-history.html
7634 bytes
0644
dblink.html
5322 bytes
0644
ddl-alter.html
10498 bytes
0644
ddl-basics.html
7816 bytes
0644
ddl-constraints.html
22790 bytes
0644
ddl-default.html
4540 bytes
0644
ddl-depend.html
6498 bytes
0644
ddl-foreign-data.html
4485 bytes
0644
ddl-inherit.html
15308 bytes
0644
ddl-others.html
3080 bytes
0644
ddl-partitioning.html
27763 bytes
0644
ddl-priv.html
6066 bytes
0644
ddl-schemas.html
18046 bytes
0644
ddl-system-columns.html
8049 bytes
0644
ddl.html
6382 bytes
0644
dict-int.html
4793 bytes
0644
dict-xsyn.html
6481 bytes
0644
different-replication-solutions.html
14793 bytes
0644
disk-full.html
3517 bytes
0644
disk-usage.html
5661 bytes
0644
diskusage.html
2668 bytes
0644
dml-delete.html
3565 bytes
0644
dml-insert.html
5801 bytes
0644
dml-returning.html
5104 bytes
0644
dml-update.html
5556 bytes
0644
dml.html
2944 bytes
0644
docguide-authoring.html
6757 bytes
0644
docguide-build.html
15280 bytes
0644
docguide-docbook.html
3853 bytes
0644
docguide-style.html
7429 bytes
0644
docguide-toolsets.html
20683 bytes
0644
docguide.html
3624 bytes
0644
dummy-seclabel.html
4358 bytes
0644
dynamic-trace.html
27234 bytes
0644
earthdistance.html
8806 bytes
0644
ecpg-commands.html
9527 bytes
0644
ecpg-concept.html
4979 bytes
0644
ecpg-connect.html
10826 bytes
0644
ecpg-cpp.html
9624 bytes
0644
ecpg-descriptors.html
34909 bytes
0644
ecpg-develop.html
7964 bytes
0644
ecpg-dynamic.html
6515 bytes
0644
ecpg-errors.html
25737 bytes
0644
ecpg-informix-compat.html
52760 bytes
0644
ecpg-library.html
5798 bytes
0644
ecpg-lo.html
5527 bytes
0644
ecpg-pgtypes.html
54457 bytes
0644
ecpg-preproc.html
8985 bytes
0644
ecpg-process.html
5386 bytes
0644
ecpg-sql-allocate-descriptor.html
3983 bytes
0644
ecpg-sql-commands.html
4698 bytes
0644
ecpg-sql-connect.html
9375 bytes
0644
ecpg-sql-deallocate-descriptor.html
3773 bytes
0644
ecpg-sql-declare.html
5397 bytes
0644
ecpg-sql-describe.html
4595 bytes
0644
ecpg-sql-disconnect.html
4733 bytes
0644
ecpg-sql-execute-immediate.html
3877 bytes
0644
ecpg-sql-get-descriptor.html
7709 bytes
0644
ecpg-sql-open.html
4642 bytes
0644
ecpg-sql-prepare.html
4177 bytes
0644
ecpg-sql-set-autocommit.html
3333 bytes
0644
ecpg-sql-set-connection.html
3929 bytes
0644
ecpg-sql-set-descriptor.html
5505 bytes
0644
ecpg-sql-type.html
5026 bytes
0644
ecpg-sql-var.html
3539 bytes
0644
ecpg-sql-whenever.html
4686 bytes
0644
ecpg-variables.html
40283 bytes
0644
ecpg.html
10344 bytes
0644
encryption-options.html
7495 bytes
0644
errcodes-appendix.html
36965 bytes
0644
error-message-reporting.html
14124 bytes
0644
error-style-guide.html
16769 bytes
0644
event-log-registration.html
4188 bytes
0644
executor.html
6612 bytes
0644
explicit-joins.html
11019 bytes
0644
explicit-locking.html
25073 bytes
0644
extend-extensions.html
32430 bytes
0644
extend-how.html
4552 bytes
0644
extend-pgxs.html
11761 bytes
0644
extend-type-system.html
10111 bytes
0644
extend.html
9982 bytes
0644
external-admin-tools.html
2722 bytes
0644
external-extensions.html
3263 bytes
0644
external-interfaces.html
5513 bytes
0644
external-pl.html
4670 bytes
0644
external-projects.html
3004 bytes
0644
fdw-callbacks.html
12905 bytes
0644
fdw-functions.html
4496 bytes
0644
fdw-helpers.html
5988 bytes
0644
fdw-planning.html
9845 bytes
0644
fdwhandler.html
3990 bytes
0644
features-sql-standard.html
39105 bytes
0644
features.html
7566 bytes
0644
file-fdw.html
7709 bytes
0644
functions-admin.html
50395 bytes
0644
functions-aggregate.html
21814 bytes
0644
functions-array.html
13521 bytes
0644
functions-binarystring.html
12588 bytes
0644
functions-bitstring.html
6786 bytes
0644
functions-comparison.html
10638 bytes
0644
functions-comparisons.html
13531 bytes
0644
functions-conditional.html
11007 bytes
0644
functions-datetime.html
48303 bytes
0644
functions-enum.html
5491 bytes
0644
functions-formatting.html
35401 bytes
0644
functions-geometry.html
20347 bytes
0644
functions-info.html
58658 bytes
0644
functions-json.html
3814 bytes
0644
functions-logical.html
4665 bytes
0644
functions-matching.html
75728 bytes
0644
functions-math.html
20401 bytes
0644
functions-net.html
13502 bytes
0644
functions-range.html
10857 bytes
0644
functions-sequence.html
12925 bytes
0644
functions-srf.html
8840 bytes
0644
functions-string.html
59052 bytes
0644
functions-subquery.html
16381 bytes
0644
functions-textsearch.html
20488 bytes
0644
functions-trigger.html
4548 bytes
0644
functions-window.html
12085 bytes
0644
functions-xml.html
32169 bytes
0644
functions.html
9939 bytes
0644
fuzzystrmatch.html
8061 bytes
0644
geqo-biblio.html
3459 bytes
0644
geqo-intro.html
4415 bytes
0644
geqo-intro2.html
5627 bytes
0644
geqo-pg-intro.html
8785 bytes
0644
geqo.html
3616 bytes
0644
gin-examples.html
3322 bytes
0644
gin-extensibility.html
14402 bytes
0644
gin-implementation.html
6564 bytes
0644
gin-intro.html
4662 bytes
0644
gin-limit.html
2817 bytes
0644
gin-tips.html
5713 bytes
0644
gin.html
2929 bytes
0644
gist-examples.html
3752 bytes
0644
gist-extensibility.html
24354 bytes
0644
gist-implementation.html
4101 bytes
0644
gist-intro.html
3616 bytes
0644
gist.html
2679 bytes
0644
git.html
4564 bytes
0644
high-availability.html
7698 bytes
0644
history.html
11918 bytes
0644
hot-standby.html
36045 bytes
0644
hstore.html
22629 bytes
0644
index-catalog.html
7996 bytes
0644
index-cost-estimation.html
9991 bytes
0644
index-functions.html
19114 bytes
0644
index-locking.html
8049 bytes
0644
index-scanning.html
10707 bytes
0644
index-unique-checks.html
9192 bytes
0644
index.html
8071 bytes
0644
indexam.html
5247 bytes
0644
indexes-bitmap-scans.html
6580 bytes
0644
indexes-collations.html
3640 bytes
0644
indexes-examine.html
7161 bytes
0644
indexes-expressional.html
4813 bytes
0644
indexes-intro.html
6313 bytes
0644
indexes-multicolumn.html
6298 bytes
0644
indexes-opclass.html
7336 bytes
0644
indexes-ordering.html
6480 bytes
0644
indexes-partial.html
11812 bytes
0644
indexes-types.html
10233 bytes
0644
indexes-unique.html
4002 bytes
0644
indexes.html
3619 bytes
0644
information-schema.html
11177 bytes
0644
infoschema-administrable-role-authorizations.html
3751 bytes
0644
infoschema-applicable-roles.html
3970 bytes
0644
infoschema-attributes.html
12807 bytes
0644
infoschema-character-sets.html
7050 bytes
0644
infoschema-check-constraint-routine-usage.html
4349 bytes
0644
infoschema-check-constraints.html
3876 bytes
0644
infoschema-collation-character-set-applicab.html
4425 bytes
0644
infoschema-collations.html
3885 bytes
0644
infoschema-column-domain-usage.html
4322 bytes
0644
infoschema-column-options.html
4109 bytes
0644
infoschema-column-privileges.html
5029 bytes
0644
infoschema-column-udt-usage.html
4583 bytes
0644
infoschema-columns.html
17625 bytes
0644
infoschema-constraint-column-usage.html
4873 bytes
0644
infoschema-constraint-table-usage.html
4774 bytes
0644
infoschema-data-type-privileges.html
5089 bytes
0644
infoschema-datatypes.html
4229 bytes
0644
infoschema-domain-constraints.html
4664 bytes
0644
infoschema-domain-udt-usage.html
4171 bytes
0644
infoschema-domains.html
11367 bytes
0644
infoschema-element-types.html
11374 bytes
0644
infoschema-enabled-roles.html
3780 bytes
0644
infoschema-foreign-data-wrapper-options.html
3910 bytes
0644
infoschema-foreign-data-wrappers.html
4227 bytes
0644
infoschema-foreign-server-options.html
3853 bytes
0644
infoschema-foreign-servers.html
4571 bytes
0644
infoschema-foreign-table-options.html
3974 bytes
0644
infoschema-foreign-tables.html
4072 bytes
0644
infoschema-information-schema-catalog-name.html
3357 bytes
0644
infoschema-key-column-usage.html
5185 bytes
0644
infoschema-parameters.html
10799 bytes
0644
infoschema-referential-constraints.html
5664 bytes
0644
infoschema-role-column-grants.html
5017 bytes
0644
infoschema-role-routine-grants.html
5360 bytes
0644
infoschema-role-table-grants.html
5427 bytes
0644
infoschema-role-udt-grants.html
4781 bytes
0644
infoschema-role-usage-grants.html
5010 bytes
0644
infoschema-routine-privileges.html
5032 bytes
0644
infoschema-routines.html
23052 bytes
0644
infoschema-schema.html
3180 bytes
0644
infoschema-schemata.html
4248 bytes
0644
infoschema-sequences.html
6111 bytes
0644
infoschema-sql-features.html
4708 bytes
0644
infoschema-sql-implementation-info.html
4503 bytes
0644
infoschema-sql-languages.html
5094 bytes
0644
infoschema-sql-packages.html
4178 bytes
0644
infoschema-sql-parts.html
4080 bytes
0644
infoschema-sql-sizing-profiles.html
4177 bytes
0644
infoschema-sql-sizing.html
4101 bytes
0644
infoschema-table-constraints.html
4914 bytes
0644
infoschema-table-privileges.html
5097 bytes
0644
infoschema-tables.html
5957 bytes
0644
infoschema-triggered-update-columns.html
4554 bytes
0644
infoschema-triggers.html
9447 bytes
0644
infoschema-udt-privileges.html
4509 bytes
0644
infoschema-usage-privileges.html
5512 bytes
0644
infoschema-user-defined-types.html
9753 bytes
0644
infoschema-user-mapping-options.html
4449 bytes
0644
infoschema-user-mappings.html
3833 bytes
0644
infoschema-view-column-usage.html
4728 bytes
0644
infoschema-view-routine-usage.html
4368 bytes
0644
infoschema-view-table-usage.html
4389 bytes
0644
infoschema-views.html
5529 bytes
0644
install-getsource.html
3574 bytes
0644
install-post.html
8076 bytes
0644
install-procedure.html
46527 bytes
0644
install-requirements.html
14481 bytes
0644
install-short.html
2870 bytes
0644
install-windows-full.html
19274 bytes
0644
install-windows-libpq.html
6283 bytes
0644
install-windows.html
6620 bytes
0644
installation-platform-notes.html
39380 bytes
0644
installation.html
4160 bytes
0644
intagg.html
6254 bytes
0644
intarray.html
13757 bytes
0644
internals.html
15638 bytes
0644
intro-whatis.html
4011 bytes
0644
isn.html
13356 bytes
0644
kernel-resources.html
37822 bytes
0644
largeobjects.html
4675 bytes
0644
libpq-async.html
21020 bytes
0644
libpq-build.html
6369 bytes
0644
libpq-cancel.html
6777 bytes
0644
libpq-connect.html
51248 bytes
0644
libpq-control.html
6280 bytes
0644
libpq-copy.html
22442 bytes
0644
libpq-envars.html
9820 bytes
0644
libpq-events.html
23093 bytes
0644
libpq-example.html
16024 bytes
0644
libpq-exec.html
64877 bytes
0644
libpq-fastpath.html
6124 bytes
0644
libpq-ldap.html
5506 bytes
0644
libpq-misc.html
13815 bytes
0644
libpq-notice-processing.html
6284 bytes
0644
libpq-notify.html
6715 bytes
0644
libpq-pgpass.html
4861 bytes
0644
libpq-pgservice.html
3905 bytes
0644
libpq-single-row-mode.html
6353 bytes
0644
libpq-ssl.html
19972 bytes
0644
libpq-status.html
17695 bytes
0644
libpq-threading.html
5544 bytes
0644
libpq.html
7918 bytes
0644
lo-examplesect.html
8696 bytes
0644
lo-funcs.html
4640 bytes
0644
lo-implementation.html
3353 bytes
0644
lo-interfaces.html
15155 bytes
0644
lo-intro.html
3206 bytes
0644
lo.html
6627 bytes
0644
locale.html
13691 bytes
0644
locking-indexes.html
4350 bytes
0644
log-shipping-alternative.html
11057 bytes
0644
logfile-maintenance.html
7143 bytes
0644
ltree.html
27295 bytes
0644
maintenance.html
5538 bytes
0644
manage-ag-config.html
3746 bytes
0644
manage-ag-createdb.html
6310 bytes
0644
manage-ag-dropdb.html
3605 bytes
0644
manage-ag-overview.html
5144 bytes
0644
manage-ag-tablespaces.html
9250 bytes
0644
manage-ag-templatedbs.html
8162 bytes
0644
managing-databases.html
3273 bytes
0644
monitoring-locks.html
3673 bytes
0644
monitoring-ps.html
6782 bytes
0644
monitoring-stats.html
58063 bytes
0644
monitoring.html
4458 bytes
0644
multibyte.html
31965 bytes
0644
mvcc-caveats.html
4077 bytes
0644
mvcc-intro.html
4552 bytes
0644
mvcc.html
4302 bytes
0644
nls-programmer.html
10078 bytes
0644
nls-translator.html
14522 bytes
0644
nls.html
3134 bytes
0644
non-durability.html
4484 bytes
0644
notation.html
4415 bytes
0644
oid2name.html
11962 bytes
0644
overview.html
4093 bytes
0644
pageinspect.html
8117 bytes
0644
parser-stage.html
8117 bytes
0644
passwordcheck.html
4788 bytes
0644
performance-tips.html
4501 bytes
0644
perm-functions.html
3338 bytes
0644
pgarchivecleanup.html
8999 bytes
0644
pgbench.html
30833 bytes
0644
pgbuffercache.html
7715 bytes
0644
pgcrypto.html
38804 bytes
0644
pgfreespacemap.html
5230 bytes
0644
pgrowlocks.html
6078 bytes
0644
pgstandby.html
15204 bytes
0644
pgstatstatements.html
16068 bytes
0644
pgstattuple.html
9449 bytes
0644
pgtestfsync.html
5254 bytes
0644
pgtesttiming.html
12476 bytes
0644
pgtrgm.html
12333 bytes
0644
pgupgrade.html
24737 bytes
0644
planner-optimizer.html
9396 bytes
0644
planner-stats-details.html
3276 bytes
0644
planner-stats-security.html
5556 bytes
0644
planner-stats.html
9058 bytes
0644
plhandler.html
13748 bytes
0644
plperl-builtins.html
18276 bytes
0644
plperl-data.html
2878 bytes
0644
plperl-funcs.html
13369 bytes
0644
plperl-global.html
5067 bytes
0644
plperl-triggers.html
6446 bytes
0644
plperl-trusted.html
6712 bytes
0644
plperl-under-the-hood.html
8991 bytes
0644
plperl.html
4930 bytes
0644
plpgsql-control-structures.html
46183 bytes
0644
plpgsql-cursors.html
25586 bytes
0644
plpgsql-declarations.html
21746 bytes
0644
plpgsql-development-tips.html
9511 bytes
0644
plpgsql-errors-and-messages.html
10094 bytes
0644
plpgsql-expressions.html
4662 bytes
0644
plpgsql-implementation.html
18043 bytes
0644
plpgsql-overview.html
9032 bytes
0644
plpgsql-porting.html
27094 bytes
0644
plpgsql-statements.html
32221 bytes
0644
plpgsql-structure.html
8329 bytes
0644
plpgsql-trigger.html
22322 bytes
0644
plpgsql.html
6965 bytes
0644
plpython-data.html
14648 bytes
0644
plpython-database.html
15413 bytes
0644
plpython-do.html
2771 bytes
0644
plpython-envar.html
3885 bytes
0644
plpython-funcs.html
5478 bytes
0644
plpython-python23.html
7207 bytes
0644
plpython-sharing.html
3032 bytes
0644
plpython-subtransaction.html
7888 bytes
0644
plpython-trigger.html
5069 bytes
0644
plpython-util.html
5104 bytes
0644
plpython.html
6067 bytes
0644
pltcl-data.html
2906 bytes
0644
pltcl-dbaccess.html
13902 bytes
0644
pltcl-functions.html
6177 bytes
0644
pltcl-global.html
5066 bytes
0644
pltcl-overview.html
5288 bytes
0644
pltcl-procnames.html
3222 bytes
0644
pltcl-trigger.html
9452 bytes
0644
pltcl-unknown.html
5075 bytes
0644
pltcl.html
3400 bytes
0644
populate.html
17114 bytes
0644
postgres-user.html
3314 bytes
0644
preface.html
5070 bytes
0644
preventing-server-spoofing.html
4604 bytes
0644
protocol-changes.html
6650 bytes
0644
protocol-error-fields.html
6131 bytes
0644
protocol-flow.html
46202 bytes
0644
protocol-message-formats.html
40844 bytes
0644
protocol-message-types.html
4933 bytes
0644
protocol-overview.html
9670 bytes
0644
protocol-replication.html
14666 bytes
0644
protocol.html
5652 bytes
0644
queries-limit.html
5335 bytes
0644
queries-order.html
7369 bytes
0644
queries-overview.html
5068 bytes
0644
queries-select-lists.html
9308 bytes
0644
queries-table-expressions.html
39874 bytes
0644
queries-union.html
5114 bytes
0644
queries-values.html
4930 bytes
0644
queries-with.html
20880 bytes
0644
queries.html
4418 bytes
0644
query-path.html
5470 bytes
0644
querytree.html
11136 bytes
0644
rangetypes.html
22735 bytes
0644
recovery-config.html
3550 bytes
0644
recovery-target-settings.html
7762 bytes
0644
reference-client.html
6102 bytes
0644
reference-server.html
3964 bytes
0644
reference.html
23162 bytes
0644
regress-coverage.html
3325 bytes
0644
regress-evaluation.html
12487 bytes
0644
regress-run.html
13710 bytes
0644
regress-variant.html
7177 bytes
0644
regress.html
4277 bytes
0644
release-0-01.html
2555 bytes
0644
release-0-02.html
4292 bytes
0644
release-0-03.html
7798 bytes
0644
release-1-0.html
4229 bytes
0644
release-1-01.html
9346 bytes
0644
release-1-02.html
6489 bytes
0644
release-1-09.html
2525 bytes
0644
release-6-0.html
7920 bytes
0644
release-6-1-1.html
3719 bytes
0644
release-6-1.html
9025 bytes
0644
release-6-2-1.html
4405 bytes
0644
release-6-2.html
8883 bytes
0644
release-6-3-1.html
4444 bytes
0644
release-6-3-2.html
4157 bytes
0644
release-6-3.html
16311 bytes
0644
release-6-4-1.html
4061 bytes
0644
release-6-4-2.html
2908 bytes
0644
release-6-4.html
14732 bytes
0644
release-6-5-1.html
3842 bytes
0644
release-6-5-2.html
4102 bytes
0644
release-6-5-3.html
3053 bytes
0644
release-6-5.html
17387 bytes
0644
release-7-0-1.html
3920 bytes
0644
release-7-0-2.html
2887 bytes
0644
release-7-0-3.html
4656 bytes
0644
release-7-0.html
23104 bytes
0644
release-7-1-1.html
3262 bytes
0644
release-7-1-2.html
2975 bytes
0644
release-7-1-3.html
3139 bytes
0644
release-7-1.html
13017 bytes
0644
release-7-2-1.html
4011 bytes
0644
release-7-2-2.html
3793 bytes
0644
release-7-2-3.html
3364 bytes
0644
release-7-2-4.html
3587 bytes
0644
release-7-2-5.html
3746 bytes
0644
release-7-2-6.html
3624 bytes
0644
release-7-2-7.html
3726 bytes
0644
release-7-2-8.html
3948 bytes
0644
release-7-2.html
27098 bytes
0644
release-7-3-1.html
4168 bytes
0644
release-7-3-10.html
7493 bytes
0644
release-7-3-11.html
4111 bytes
0644
release-7-3-12.html
3527 bytes
0644
release-7-3-13.html
4618 bytes
0644
release-7-3-14.html
3931 bytes
0644
release-7-3-15.html
6315 bytes
0644
release-7-3-16.html
3424 bytes
0644
release-7-3-17.html
3550 bytes
0644
release-7-3-18.html
3647 bytes
0644
release-7-3-19.html
3686 bytes
0644
release-7-3-2.html
5205 bytes
0644
release-7-3-20.html
3524 bytes
0644
release-7-3-21.html
6216 bytes
0644
release-7-3-3.html
10290 bytes
0644
release-7-3-4.html
3502 bytes
0644
release-7-3-5.html
4493 bytes
0644
release-7-3-6.html
4428 bytes
0644
release-7-3-7.html
3352 bytes
0644
release-7-3-8.html
3571 bytes
0644
release-7-3-9.html
4079 bytes
0644
release-7-3.html
33053 bytes
0644
release-7-4-1.html
7116 bytes
0644
release-7-4-10.html
3806 bytes
0644
release-7-4-11.html
4857 bytes
0644
release-7-4-12.html
4221 bytes
0644
release-7-4-13.html
6961 bytes
0644
release-7-4-14.html
3673 bytes
0644
release-7-4-15.html
4270 bytes
0644
release-7-4-16.html
3972 bytes
0644
release-7-4-17.html
4013 bytes
0644
release-7-4-18.html
3927 bytes
0644
release-7-4-19.html
7242 bytes
0644
release-7-4-2.html
8260 bytes
0644
release-7-4-20.html
6605 bytes
0644
release-7-4-21.html
3922 bytes
0644
release-7-4-22.html
4071 bytes
0644
release-7-4-23.html
4423 bytes
0644
release-7-4-24.html
4289 bytes
0644
release-7-4-25.html
4506 bytes
0644
release-7-4-26.html
5455 bytes
0644
release-7-4-27.html
5164 bytes
0644
release-7-4-28.html
5629 bytes
0644
release-7-4-29.html
6960 bytes
0644
release-7-4-3.html
4615 bytes
0644
release-7-4-30.html
6211 bytes
0644
release-7-4-4.html
4085 bytes
0644
release-7-4-5.html
3194 bytes
0644
release-7-4-6.html
4731 bytes
0644
release-7-4-7.html
4274 bytes
0644
release-7-4-8.html
10156 bytes
0644
release-7-4-9.html
5118 bytes
0644
release-7-4.html
57378 bytes
0644
release-8-0-1.html
4744 bytes
0644
release-8-0-10.html
4751 bytes
0644
release-8-0-11.html
3969 bytes
0644
release-8-0-12.html
3134 bytes
0644
release-8-0-13.html
4118 bytes
0644
release-8-0-14.html
4518 bytes
0644
release-8-0-15.html
9101 bytes
0644
release-8-0-16.html
8946 bytes
0644
release-8-0-17.html
3920 bytes
0644
release-8-0-18.html
5579 bytes
0644
release-8-0-19.html
4976 bytes
0644
release-8-0-2.html
9566 bytes
0644
release-8-0-20.html
4312 bytes
0644
release-8-0-21.html
4504 bytes
0644
release-8-0-22.html
6440 bytes
0644
release-8-0-23.html
6023 bytes
0644
release-8-0-24.html
7002 bytes
0644
release-8-0-25.html
7427 bytes
0644
release-8-0-26.html
8026 bytes
0644
release-8-0-3.html
7425 bytes
0644
release-8-0-4.html
6680 bytes
0644
release-8-0-5.html
4816 bytes
0644
release-8-0-6.html
5694 bytes
0644
release-8-0-7.html
5909 bytes
0644
release-8-0-8.html
7225 bytes
0644
release-8-0-9.html
4306 bytes
0644
release-8-0.html
66818 bytes
0644
release-8-1-1.html
5459 bytes
0644
release-8-1-10.html
4781 bytes
0644
release-8-1-11.html
9946 bytes
0644
release-8-1-12.html
9341 bytes
0644
release-8-1-13.html
4292 bytes
0644
release-8-1-14.html
6901 bytes
0644
release-8-1-15.html
6274 bytes
0644
release-8-1-16.html
5278 bytes
0644
release-8-1-17.html
6035 bytes
0644
release-8-1-18.html
6442 bytes
0644
release-8-1-19.html
6612 bytes
0644
release-8-1-2.html
6335 bytes
0644
release-8-1-20.html
7298 bytes
0644
release-8-1-21.html
7213 bytes
0644
release-8-1-22.html
8324 bytes
0644
release-8-1-23.html
7933 bytes
0644
release-8-1-3.html
7026 bytes
0644
release-8-1-4.html
8873 bytes
0644
release-8-1-5.html
5479 bytes
0644
release-8-1-6.html
5337 bytes
0644
release-8-1-7.html
4558 bytes
0644
release-8-1-8.html
3116 bytes
0644
release-8-1-9.html
4388 bytes
0644
release-8-1.html
62113 bytes
0644
release-8-2-1.html
5065 bytes
0644
release-8-2-10.html
8180 bytes
0644
release-8-2-11.html
7147 bytes
0644
release-8-2-12.html
6748 bytes
0644
release-8-2-13.html
7348 bytes
0644
release-8-2-14.html
7876 bytes
0644
release-8-2-15.html
8155 bytes
0644
release-8-2-16.html
9293 bytes
0644
release-8-2-17.html
8214 bytes
0644
release-8-2-18.html
10277 bytes
0644
release-8-2-19.html
8589 bytes
0644
release-8-2-2.html
5802 bytes
0644
release-8-2-20.html
6244 bytes
0644
release-8-2-21.html
5593 bytes
0644
release-8-2-22.html
9617 bytes
0644
release-8-2-23.html
9559 bytes
0644
release-8-2-3.html
3095 bytes
0644
release-8-2-4.html
5428 bytes
0644
release-8-2-5.html
5995 bytes
0644
release-8-2-6.html
10551 bytes
0644
release-8-2-7.html
9311 bytes
0644
release-8-2-8.html
7521 bytes
0644
release-8-2-9.html
4281 bytes
0644
release-8-2.html
69398 bytes
0644
release-8-3-1.html
10585 bytes
0644
release-8-3-10.html
10725 bytes
0644
release-8-3-11.html
8963 bytes
0644
release-8-3-12.html
12119 bytes
0644
release-8-3-13.html
9506 bytes
0644
release-8-3-14.html
6242 bytes
0644
release-8-3-15.html
6381 bytes
0644
release-8-3-16.html
11015 bytes
0644
release-8-3-17.html
10590 bytes
0644
release-8-3-18.html
11265 bytes
0644
release-8-3-19.html
8466 bytes
0644
release-8-3-2.html
12203 bytes
0644
release-8-3-20.html
9251 bytes
0644
release-8-3-21.html
5034 bytes
0644
release-8-3-22.html
10585 bytes
0644
release-8-3-23.html
6284 bytes
0644
release-8-3-3.html
4275 bytes
0644
release-8-3-4.html
11273 bytes
0644
release-8-3-5.html
8689 bytes
0644
release-8-3-6.html
9197 bytes
0644
release-8-3-7.html
9729 bytes
0644
release-8-3-8.html
9260 bytes
0644
release-8-3-9.html
10206 bytes
0644
release-8-3.html
69773 bytes
0644
release-8-4-1.html
9563 bytes
0644
release-8-4-10.html
11932 bytes
0644
release-8-4-11.html
13787 bytes
0644
release-8-4-12.html
9987 bytes
0644
release-8-4-13.html
9714 bytes
0644
release-8-4-14.html
5117 bytes
0644
release-8-4-15.html
10626 bytes
0644
release-8-4-16.html
7329 bytes
0644
release-8-4-17.html
9572 bytes
0644
release-8-4-18.html
7048 bytes
0644
release-8-4-19.html
7780 bytes
0644
release-8-4-2.html
15697 bytes
0644
release-8-4-20.html
16258 bytes
0644
release-8-4-21.html
5450 bytes
0644
release-8-4-22.html
11306 bytes
0644
release-8-4-3.html
13928 bytes
0644
release-8-4-4.html
10736 bytes
0644
release-8-4-5.html
15933 bytes
0644
release-8-4-6.html
10430 bytes
0644
release-8-4-7.html
6220 bytes
0644
release-8-4-8.html
8850 bytes
0644
release-8-4-9.html
14528 bytes
0644
release-8-4.html
87976 bytes
0644
release-9-0-1.html
5946 bytes
0644
release-9-0-10.html
5693 bytes
0644
release-9-0-11.html
12666 bytes
0644
release-9-0-12.html
8824 bytes
0644
release-9-0-13.html
11671 bytes
0644
release-9-0-14.html
8759 bytes
0644
release-9-0-15.html
9147 bytes
0644
release-9-0-16.html
17408 bytes
0644
release-9-0-17.html
6335 bytes
0644
release-9-0-18.html
11879 bytes
0644
release-9-0-19.html
26610 bytes
0644
release-9-0-2.html
13636 bytes
0644
release-9-0-20.html
15836 bytes
0644
release-9-0-21.html
5166 bytes
0644
release-9-0-22.html
4321 bytes
0644
release-9-0-23.html
16158 bytes
0644
release-9-0-3.html
7256 bytes
0644
release-9-0-4.html
11345 bytes
0644
release-9-0-5.html
17915 bytes
0644
release-9-0-6.html
13426 bytes
0644
release-9-0-7.html
18091 bytes
0644
release-9-0-8.html
10993 bytes
0644
release-9-0-9.html
11743 bytes
0644
release-9-0.html
96127 bytes
0644
release-9-1-1.html
3670 bytes
0644
release-9-1-10.html
10352 bytes
0644
release-9-1-11.html
9584 bytes
0644
release-9-1-12.html
18554 bytes
0644
release-9-1-13.html
6685 bytes
0644
release-9-1-14.html
13036 bytes
0644
release-9-1-15.html
28969 bytes
0644
release-9-1-16.html
19119 bytes
0644
release-9-1-17.html
4947 bytes
0644
release-9-1-18.html
4102 bytes
0644
release-9-1-19.html
17617 bytes
0644
release-9-1-2.html
21571 bytes
0644
release-9-1-20.html
17541 bytes
0644
release-9-1-21.html
7601 bytes
0644
release-9-1-22.html
7258 bytes
0644
release-9-1-23.html
12653 bytes
0644
release-9-1-24.html
8731 bytes
0644
release-9-1-3.html
21153 bytes
0644
release-9-1-4.html
16018 bytes
0644
release-9-1-5.html
14042 bytes
0644
release-9-1-6.html
9521 bytes
0644
release-9-1-7.html
14941 bytes
0644
release-9-1-8.html
10154 bytes
0644
release-9-1-9.html
12679 bytes
0644
release-9-1.html
78963 bytes
0644
release-9-2-1.html
7111 bytes
0644
release-9-2-10.html
32368 bytes
0644
release-9-2-11.html
20298 bytes
0644
release-9-2-12.html
5130 bytes
0644
release-9-2-13.html
4102 bytes
0644
release-9-2-14.html
18386 bytes
0644
release-9-2-15.html
18605 bytes
0644
release-9-2-16.html
7598 bytes
0644
release-9-2-17.html
8195 bytes
0644
release-9-2-18.html
12718 bytes
0644
release-9-2-19.html
10514 bytes
0644
release-9-2-2.html
23001 bytes
0644
release-9-2-20.html
13332 bytes
0644
release-9-2-21.html
14198 bytes
0644
release-9-2-22.html
15865 bytes
0644
release-9-2-23.html
8126 bytes
0644
release-9-2-24.html
7877 bytes
0644
release-9-2-3.html
13373 bytes
0644
release-9-2-4.html
14800 bytes
0644
release-9-2-5.html
12005 bytes
0644
release-9-2-6.html
11684 bytes
0644
release-9-2-7.html
20022 bytes
0644
release-9-2-8.html
7375 bytes
0644
release-9-2-9.html
15615 bytes
0644
release-9-2.html
79519 bytes
0644
release.html
22882 bytes
0644
resources.html
4226 bytes
0644
role-attributes.html
7855 bytes
0644
role-membership.html
8390 bytes
0644
role-removal.html
5303 bytes
0644
routine-reindex.html
3628 bytes
0644
routine-vacuuming.html
38023 bytes
0644
row-estimation-examples.html
20767 bytes
0644
rowtypes.html
23412 bytes
0644
rule-system.html
4117 bytes
0644
rules-privileges.html
11663 bytes
0644
rules-status.html
4512 bytes
0644
rules-triggers.html
9476 bytes
0644
rules-update.html
32615 bytes
0644
rules-views.html
26888 bytes
0644
rules.html
4948 bytes
0644
runtime-config-autovacuum.html
10974 bytes
0644
runtime-config-client.html
32815 bytes
0644
runtime-config-compatible.html
14827 bytes
0644
runtime-config-connection.html
23478 bytes
0644
runtime-config-custom.html
3548 bytes
0644
runtime-config-developer.html
14070 bytes
0644
runtime-config-error-handling.html
3570 bytes
0644
runtime-config-file-locations.html
6977 bytes
0644
runtime-config-locks.html
7634 bytes
0644
runtime-config-logging.html
45446 bytes
0644
runtime-config-preset.html
8710 bytes
0644
runtime-config-query.html
24950 bytes
0644
runtime-config-replication.html
18294 bytes
0644
runtime-config-resource.html
27901 bytes
0644
runtime-config-short.html
6683 bytes
0644
runtime-config-statistics.html
8616 bytes
0644
runtime-config-wal.html
27093 bytes
0644
runtime-config.html
8249 bytes
0644
runtime.html
5241 bytes
0644
seg.html
15470 bytes
0644
sepgsql.html
30829 bytes
0644
server-programming.html
9618 bytes
0644
server-shutdown.html
6469 bytes
0644
server-start.html
14217 bytes
0644
source-format.html
5133 bytes
0644
source.html
4071 bytes
0644
sourcerepo.html
3411 bytes
0644
spgist-examples.html
2703 bytes
0644
spgist-extensibility.html
31282 bytes
0644
spgist-implementation.html
8098 bytes
0644
spgist-intro.html
4323 bytes
0644
spgist.html
2966 bytes
0644
spi-examples.html
6217 bytes
0644
spi-interface-support.html
3770 bytes
0644
spi-interface.html
5998 bytes
0644
spi-memory.html
7089 bytes
0644
spi-realloc.html
3627 bytes
0644
spi-spi-connect.html
4052 bytes
0644
spi-spi-copytuple.html
3453 bytes
0644
spi-spi-cursor-close.html
3336 bytes
0644
spi-spi-cursor-fetch.html
4110 bytes
0644
spi-spi-cursor-find.html
3464 bytes
0644
spi-spi-cursor-move.html
3890 bytes
0644
spi-spi-cursor-open-with-args.html
6178 bytes
0644
spi-spi-cursor-open-with-paramlist.html
5035 bytes
0644
spi-spi-cursor-open.html
5732 bytes
0644
spi-spi-exec.html
3591 bytes
0644
spi-spi-execp.html
4866 bytes
0644
spi-spi-execute-plan-with-paramlist.html
4893 bytes
0644
spi-spi-execute-plan.html
5901 bytes
0644
spi-spi-execute-with-args.html
6221 bytes
0644
spi-spi-execute.html
12598 bytes
0644
spi-spi-finish.html
3655 bytes
0644
spi-spi-fname.html
3767 bytes
0644
spi-spi-fnumber.html
3936 bytes
0644
spi-spi-freeplan.html
3505 bytes
0644
spi-spi-freetuple.html
3277 bytes
0644
spi-spi-freetupletable.html
3628 bytes
0644
spi-spi-getargcount.html
3698 bytes
0644
spi-spi-getargtypeid.html
4141 bytes
0644
spi-spi-getbinval.html
4287 bytes
0644
spi-spi-getnspname.html
3467 bytes
0644
spi-spi-getrelname.html
3351 bytes
0644
spi-spi-gettype.html
3714 bytes
0644
spi-spi-gettypeid.html
3718 bytes
0644
spi-spi-getvalue.html
4166 bytes
0644
spi-spi-is-cursor-plan.html
4560 bytes
0644
spi-spi-keepplan.html
3884 bytes
0644
spi-spi-modifytuple.html
5631 bytes
0644
spi-spi-palloc.html
3157 bytes
0644
spi-spi-pfree.html
3275 bytes
0644
spi-spi-pop.html
2743 bytes
0644
spi-spi-prepare-cursor.html
5055 bytes
0644
spi-spi-prepare-params.html
4412 bytes
0644
spi-spi-prepare.html
7661 bytes
0644
spi-spi-push.html
3737 bytes
0644
spi-spi-returntuple.html
4097 bytes
0644
spi-spi-saveplan.html
4576 bytes
0644
spi-spi-scroll-cursor-fetch.html
4809 bytes
0644
spi-spi-scroll-cursor-move.html
4899 bytes
0644
spi-visibility.html
4152 bytes
0644
spi.html
10843 bytes
0644
sql-abort.html
4177 bytes
0644
sql-alteraggregate.html
6111 bytes
0644
sql-altercollation.html
5084 bytes
0644
sql-alterconversion.html
5170 bytes
0644
sql-alterdatabase.html
8778 bytes
0644
sql-alterdefaultprivileges.html
9407 bytes
0644
sql-alterdomain.html
11113 bytes
0644
sql-alterextension.html
11745 bytes
0644
sql-alterforeigndatawrapper.html
7378 bytes
0644
sql-alterforeigntable.html
12707 bytes
0644
sql-alterfunction.html
12845 bytes
0644
sql-altergroup.html
5239 bytes
0644
sql-alterindex.html
7655 bytes
0644
sql-alterlanguage.html
4022 bytes
0644
sql-alterlargeobject.html
3730 bytes
0644
sql-alteropclass.html
5114 bytes
0644
sql-alteroperator.html
5435 bytes
0644
sql-alteropfamily.html
13564 bytes
0644
sql-alterrole.html
13028 bytes
0644
sql-alterschema.html
4314 bytes
0644
sql-altersequence.html
13031 bytes
0644
sql-alterserver.html
5928 bytes
0644
sql-altertable.html
43543 bytes
0644
sql-altertablespace.html
5866 bytes
0644
sql-altertrigger.html
4647 bytes
0644
sql-altertsconfig.html
8126 bytes
0644
sql-altertsdictionary.html
6539 bytes
0644
sql-altertsparser.html
4257 bytes
0644
sql-altertstemplate.html
4223 bytes
0644
sql-altertype.html
11193 bytes
0644
sql-alteruser.html
4720 bytes
0644
sql-alterusermapping.html
5714 bytes
0644
sql-alterview.html
6969 bytes
0644
sql-analyze.html
10674 bytes
0644
sql-begin.html
6695 bytes
0644
sql-checkpoint.html
3758 bytes
0644
sql-close.html
4984 bytes
0644
sql-cluster.html
9404 bytes
0644
sql-commands.html
18810 bytes
0644
sql-comment.html
13799 bytes
0644
sql-commit-prepared.html
4516 bytes
0644
sql-commit.html
3992 bytes
0644
sql-copy.html
37443 bytes
0644
sql-createaggregate.html
13829 bytes
0644
sql-createcast.html
19632 bytes
0644
sql-createcollation.html
6739 bytes
0644
sql-createconversion.html
6538 bytes
0644
sql-createdatabase.html
12133 bytes
0644
sql-createdomain.html
8544 bytes
0644
sql-createextension.html
9083 bytes
0644
sql-createforeigndatawrapper.html
8059 bytes
0644
sql-createforeigntable.html
7718 bytes
0644
sql-createfunction.html
31076 bytes
0644
sql-creategroup.html
4012 bytes
0644
sql-createindex.html
25934 bytes
0644
sql-createlanguage.html
14888 bytes
0644
sql-createopclass.html
12676 bytes
0644
sql-createoperator.html
10688 bytes
0644
sql-createopfamily.html
5626 bytes
0644
sql-createrole.html
19325 bytes
0644
sql-createrule.html
12656 bytes
0644
sql-createschema.html
8319 bytes
0644
sql-createsequence.html
13862 bytes
0644
sql-createserver.html
6251 bytes
0644
sql-createtable.html
59172 bytes
0644
sql-createtableas.html
12772 bytes
0644
sql-createtablespace.html
6104 bytes
0644
sql-createtrigger.html
23175 bytes
0644
sql-createtsconfig.html
5352 bytes
0644
sql-createtsdictionary.html
5533 bytes
0644
sql-createtsparser.html
5947 bytes
0644
sql-createtstemplate.html
5437 bytes
0644
sql-createtype.html
39460 bytes
0644
sql-createuser.html
4524 bytes
0644
sql-createusermapping.html
5503 bytes
0644
sql-createview.html
10556 bytes
0644
sql-deallocate.html
3785 bytes
0644
sql-declare.html
15400 bytes
0644
sql-delete.html
11777 bytes
0644
sql-discard.html
4309 bytes
0644
sql-do.html
5204 bytes
0644
sql-drop-owned.html
5058 bytes
0644
sql-dropaggregate.html
4561 bytes
0644
sql-dropcast.html
4344 bytes
0644
sql-dropcollation.html
4409 bytes
0644
sql-dropconversion.html
4437 bytes
0644
sql-dropdatabase.html
4344 bytes
0644
sql-dropdomain.html
4257 bytes
0644
sql-dropextension.html
4785 bytes
0644
sql-dropforeigndatawrapper.html
4526 bytes
0644
sql-dropforeigntable.html
4560 bytes
0644
sql-dropfunction.html
5838 bytes
0644
sql-dropgroup.html
3047 bytes
0644
sql-dropindex.html
5182 bytes
0644
sql-droplanguage.html
4841 bytes
0644
sql-dropopclass.html
5678 bytes
0644
sql-dropoperator.html
5222 bytes
0644
sql-dropopfamily.html
5279 bytes
0644
sql-droprole.html
5158 bytes
0644
sql-droprule.html
4151 bytes
0644
sql-dropschema.html
4529 bytes
0644
sql-dropsequence.html
4367 bytes
0644
sql-dropserver.html
4265 bytes
0644
sql-droptable.html
5028 bytes
0644
sql-droptablespace.html
4585 bytes
0644
sql-droptrigger.html
4711 bytes
0644
sql-droptsconfig.html
4772 bytes
0644
sql-droptsdictionary.html
4689 bytes
0644
sql-droptsparser.html
4595 bytes
0644
sql-droptstemplate.html
4567 bytes
0644
sql-droptype.html
4463 bytes
0644
sql-dropuser.html
3181 bytes
0644
sql-dropusermapping.html
4679 bytes
0644
sql-dropview.html
4262 bytes
0644
sql-end.html
4157 bytes
0644
sql-execute.html
5073 bytes
0644
sql-explain.html
17094 bytes
0644
sql-expressions.html
47801 bytes
0644
sql-fetch.html
14251 bytes
0644
sql-grant.html
29245 bytes
0644
sql-insert.html
12860 bytes
0644
sql-keywords-appendix.html
106534 bytes
0644
sql-listen.html
5903 bytes
0644
sql-load.html
4207 bytes
0644
sql-lock.html
11869 bytes
0644
sql-move.html
4984 bytes
0644
sql-notify.html
10948 bytes
0644
sql-prepare-transaction.html
8640 bytes
0644
sql-prepare.html
9181 bytes
0644
sql-reassign-owned.html
5344 bytes
0644
sql-reindex.html
11103 bytes
0644
sql-release-savepoint.html
5005 bytes
0644
sql-reset.html
4993 bytes
0644
sql-revoke.html
14879 bytes
0644
sql-rollback-prepared.html
4627 bytes
0644
sql-rollback-to.html
6401 bytes
0644
sql-rollback.html
3996 bytes
0644
sql-savepoint.html
5605 bytes
0644
sql-security-label.html
8879 bytes
0644
sql-select.html
79544 bytes
0644
sql-selectinto.html
7634 bytes
0644
sql-set-constraints.html
7068 bytes
0644
sql-set-role.html
6915 bytes
0644
sql-set-session-authorization.html
6062 bytes
0644
sql-set-transaction.html
12696 bytes
0644
sql-set.html
12057 bytes
0644
sql-show.html
6851 bytes
0644
sql-start-transaction.html
4983 bytes
0644
sql-syntax-calling-funcs.html
8080 bytes
0644
sql-syntax-lexical.html
43370 bytes
0644
sql-syntax.html
5430 bytes
0644
sql-truncate.html
9364 bytes
0644
sql-unlisten.html
4923 bytes
0644
sql-update.html
15669 bytes
0644
sql-vacuum.html
10669 bytes
0644
sql-values.html
10640 bytes
0644
sql.html
13569 bytes
0644
ssh-tunnels.html
6263 bytes
0644
ssl-tcp.html
13477 bytes
0644
sslinfo.html
7594 bytes
0644
standby-settings.html
5427 bytes
0644
storage-file-layout.html
12936 bytes
0644
storage-fsm.html
3821 bytes
0644
storage-init.html
2760 bytes
0644
storage-page-layout.html
13891 bytes
0644
storage-toast.html
11478 bytes
0644
storage-vm.html
3540 bytes
0644
storage.html
2952 bytes
0644
stylesheet.css
1538 bytes
0644
supported-platforms.html
5042 bytes
0644
tablefunc.html
32193 bytes
0644
tcn.html
4974 bytes
0644
test-parser.html
4530 bytes
0644
textsearch-configuration.html
6257 bytes
0644
textsearch-controls.html
26966 bytes
0644
textsearch-debugging.html
17227 bytes
0644
textsearch-dictionaries.html
31261 bytes
0644
textsearch-features.html
21310 bytes
0644
textsearch-indexes.html
7387 bytes
0644
textsearch-intro.html
18453 bytes
0644
textsearch-limitations.html
3859 bytes
0644
textsearch-migration.html
5034 bytes
0644
textsearch-parsers.html
9210 bytes
0644
textsearch-psql.html
9345 bytes
0644
textsearch-tables.html
9750 bytes
0644
textsearch.html
5878 bytes
0644
transaction-iso.html
27240 bytes
0644
trigger-datachanges.html
5072 bytes
0644
trigger-definition.html
15507 bytes
0644
trigger-example.html
7749 bytes
0644
trigger-interface.html
10719 bytes
0644
triggers.html
3798 bytes
0644
tsearch2.html
9950 bytes
0644
tutorial-accessdb.html
7040 bytes
0644
tutorial-advanced-intro.html
3341 bytes
0644
tutorial-advanced.html
2856 bytes
0644
tutorial-agg.html
7594 bytes
0644
tutorial-arch.html
4852 bytes
0644
tutorial-concepts.html
3839 bytes
0644
tutorial-conclusion.html
2849 bytes
0644
tutorial-createdb.html
9200 bytes
0644
tutorial-delete.html
3517 bytes
0644
tutorial-fk.html
4422 bytes
0644
tutorial-inheritance.html
6137 bytes
0644
tutorial-install.html
4522 bytes
0644
tutorial-join.html
9685 bytes
0644
tutorial-populate.html
4839 bytes
0644
tutorial-select.html
8033 bytes
0644
tutorial-sql-intro.html
4904 bytes
0644
tutorial-sql.html
3060 bytes
0644
tutorial-start.html
2629 bytes
0644
tutorial-table.html
5704 bytes
0644
tutorial-transactions.html
9948 bytes
0644
tutorial-update.html
3159 bytes
0644
tutorial-views.html
3375 bytes
0644
tutorial-window.html
12481 bytes
0644
tutorial.html
5209 bytes
0644
typeconv-func.html
12170 bytes
0644
typeconv-oper.html
14907 bytes
0644
typeconv-overview.html
8301 bytes
0644
typeconv-query.html
5450 bytes
0644
typeconv-union-case.html
6612 bytes
0644
typeconv.html
3721 bytes
0644
unaccent.html
6742 bytes
0644
unsupported-features-sql-standard.html
35115 bytes
0644
upgrading.html
12795 bytes
0644
user-manag.html
3983 bytes
0644
using-explain.html
41824 bytes
0644
uuid-ossp.html
7228 bytes
0644
vacuumlo.html
7548 bytes
0644
view-pg-available-extension-versions.html
4642 bytes
0644
view-pg-available-extensions.html
3944 bytes
0644
view-pg-cursors.html
5669 bytes
0644
view-pg-group.html
3897 bytes
0644
view-pg-indexes.html
4155 bytes
0644
view-pg-locks.html
14444 bytes
0644
view-pg-prepared-statements.html
5060 bytes
0644
view-pg-prepared-xacts.html
4912 bytes
0644
view-pg-roles.html
6073 bytes
0644
view-pg-rules.html
3999 bytes
0644
view-pg-seclabels.html
5123 bytes
0644
view-pg-settings.html
10600 bytes
0644
view-pg-shadow.html
5381 bytes
0644
view-pg-stats.html
8887 bytes
0644
view-pg-tables.html
4836 bytes
0644
view-pg-timezone-abbrevs.html
3860 bytes
0644
view-pg-timezone-names.html
4177 bytes
0644
view-pg-user-mappings.html
5165 bytes
0644
view-pg-user.html
4517 bytes
0644
view-pg-views.html
3853 bytes
0644
views-overview.html
6542 bytes
0644
wal-async-commit.html
9016 bytes
0644
wal-configuration.html
14960 bytes
0644
wal-internals.html
6151 bytes
0644
wal-intro.html
5534 bytes
0644
wal-reliability.html
11479 bytes
0644
wal.html
2928 bytes
0644
warm-standby-failover.html
6102 bytes
0644
warm-standby.html
34646 bytes
0644
xaggr.html
9902 bytes
0644
xfunc-c.html
78520 bytes
0644
xfunc-internal.html
4004 bytes
0644
xfunc-overload.html
5911 bytes
0644
xfunc-pl.html
2991 bytes
0644
xfunc-sql.html
38027 bytes
0644
xfunc-volatility.html
9839 bytes
0644
xfunc.html
4518 bytes
0644
xindex.html
44593 bytes
0644
xml2.html
16900 bytes
0644
xoper-optimization.html
23144 bytes
0644
xoper.html
4835 bytes
0644
xplang-install.html
11127 bytes
0644
xplang.html
4235 bytes
0644
xtypes.html
12114 bytes
0644
N4ST4R_ID | Naxtarrr