{"kind": "relopts", "major": "18", "rows": [{"slug": "btree-deduplicate-items", "name": "deduplicate_items", "name_zh": "deduplicate_items", "category": "B-tree indexes", "summary": "Controls usage of the B-tree deduplication technique described in Section 65.1.4.3 . Set to ON or OFF to enable or disable the optimization. (Alternative spellings of ON and OFF are allowed as described in Section 19.1 .) The default is ON .", "aliases": ["btree.deduplicate_items"], "versions": {"13": {"facts": [{"label": "Applies to", "value": "B-tree indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "ON"}], "related": [{"url": "/docs/sql/create-index/?v=13", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createindex.html#INDEX-RELOPTION-DEDUPLICATE-ITEMS", "path": "sql-createindex.html", "label": "PostgreSQL 13 English manual", "sha256": "a02f612ec64fc7396ab65a1ce4458cd6971bbd8715e2465ae3c5927d20af3840"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to B-tree indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (deduplicate_items = value)", "description": ["Controls usage of the B-tree deduplication technique described in Section 63.4.2 . Set to ON or OFF to enable or disable the optimization. (Alternative spellings of ON and OFF are allowed as described in Section 19.1 .) The default is ON .", "Turning deduplicate_items off via ALTER INDEX prevents future insertions from triggering deduplication, but does not in itself make existing posting list tuples use the standard tuple representation."]}, "14": {"facts": [{"label": "Applies to", "value": "B-tree indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "ON"}], "related": [{"url": "/docs/sql/create-index/?v=14", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createindex.html#INDEX-RELOPTION-DEDUPLICATE-ITEMS", "path": "sql-createindex.html", "label": "PostgreSQL 14 English manual", "sha256": "f4d42bd08081490a491dc7bf4fa78b2a49da55ebcd0e7f843862548f7c66d70d"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to B-tree indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (deduplicate_items = value)", "description": ["Controls usage of the B-tree deduplication technique described in Section 64.4.3 . Set to ON or OFF to enable or disable the optimization. (Alternative spellings of ON and OFF are allowed as described in Section 20.1 .) The default is ON .", "Turning deduplicate_items off via ALTER INDEX prevents future insertions from triggering deduplication, but does not in itself make existing posting list tuples use the standard tuple representation."]}, "15": {"facts": [{"label": "Applies to", "value": "B-tree indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "ON"}], "related": [{"url": "/docs/sql/create-index/?v=15", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createindex.html#INDEX-RELOPTION-DEDUPLICATE-ITEMS", "path": "sql-createindex.html", "label": "PostgreSQL 15 English manual", "sha256": "d0c693e7bccb80a261cfefed9f515fd2d24fb49395dfcbd61672d7915fa0666c"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to B-tree indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (deduplicate_items = value)", "description": ["Controls usage of the B-tree deduplication technique described in Section 67.4.3 . Set to ON or OFF to enable or disable the optimization. (Alternative spellings of ON and OFF are allowed as described in Section 20.1 .) The default is ON .", "Turning deduplicate_items off via ALTER INDEX prevents future insertions from triggering deduplication, but does not in itself make existing posting list tuples use the standard tuple representation."]}, "16": {"facts": [{"label": "Applies to", "value": "B-tree indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "ON"}], "related": [{"url": "/docs/sql/create-index/?v=16", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createindex.html#INDEX-RELOPTION-DEDUPLICATE-ITEMS", "path": "sql-createindex.html", "label": "PostgreSQL 16 English manual", "sha256": "ede5053e24573587783eee1735daf6cba76010c2773f10ad066d8cdaf7073c83"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to B-tree indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (deduplicate_items = value)", "description": ["Controls usage of the B-tree deduplication technique described in Section 67.4.3 . Set to ON or OFF to enable or disable the optimization. (Alternative spellings of ON and OFF are allowed as described in Section 20.1 .) The default is ON .", "Turning deduplicate_items off via ALTER INDEX prevents future insertions from triggering deduplication, but does not in itself make existing posting list tuples use the standard tuple representation."]}, "17": {"facts": [{"label": "Applies to", "value": "B-tree indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "ON"}], "related": [{"url": "/docs/sql/create-index/?v=17", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createindex.html#INDEX-RELOPTION-DEDUPLICATE-ITEMS", "path": "sql-createindex.html", "label": "PostgreSQL 17 English manual", "sha256": "7fdb46b4a32c524457958417502f4036888552e0577352ee66f107019bbfffd6"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to B-tree indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (deduplicate_items = value)", "description": ["Controls usage of the B-tree deduplication technique described in Section 64.1.4.3 . Set to ON or OFF to enable or disable the optimization. (Alternative spellings of ON and OFF are allowed as described in Section 19.1 .) The default is ON .", "Turning deduplicate_items off via ALTER INDEX prevents future insertions from triggering deduplication, but does not in itself make existing posting list tuples use the standard tuple representation."]}, "18": {"facts": [{"label": "Applies to", "value": "B-tree indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "ON"}], "related": [{"url": "/docs/sql/create-index/?v=18", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createindex.html#INDEX-RELOPTION-DEDUPLICATE-ITEMS", "path": "sql-createindex.html", "label": "PostgreSQL 18 English manual", "sha256": "6aa00da55815d13d0355dd25cb1cdb603fa36964993f164d1b6f486011282580"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to B-tree indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (deduplicate_items = value)", "description": ["Controls usage of the B-tree deduplication technique described in Section 65.1.4.3 . Set to ON or OFF to enable or disable the optimization. (Alternative spellings of ON and OFF are allowed as described in Section 19.1 .) The default is ON .", "Turning deduplicate_items off via ALTER INDEX prevents future insertions from triggering deduplication, but does not in itself make existing posting list tuples use the standard tuple representation."]}, "19": {"facts": [{"label": "Applies to", "value": "B-tree indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "ON"}], "related": [{"url": "/docs/sql/create-index/?v=19", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createindex.html#INDEX-RELOPTION-DEDUPLICATE-ITEMS", "path": "sql-createindex.html", "label": "PostgreSQL 19 English manual", "sha256": "e90c2051c335f6636fb68f3b03f98c3282445c537c99fd7d2e74e4943662e224"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to B-tree indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (deduplicate_items = value)", "description": ["Controls usage of the B-tree deduplication technique described in Section 65.1.4.3 . Set to ON or OFF to enable or disable the optimization. (Alternative spellings of ON and OFF are allowed as described in Section 19.1 .) The default is ON .", "Turning deduplicate_items off via ALTER INDEX prevents future insertions from triggering deduplication, but does not in itself make existing posting list tuples use the standard tuple representation."]}, "20": {"facts": [{"label": "Applies to", "value": "B-tree indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "ON"}], "related": [{"url": "/docs/sql/create-index/?v=20", "label": "CREATE INDEX"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createindex.html#INDEX-RELOPTION-DEDUPLICATE-ITEMS", "path": "sql-createindex.html", "label": "PostgreSQL 20 English manual", "sha256": "33a4425c008678a8009be08f283f4f536180f45ebf9f6c2183f06daa3cf385d8"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to B-tree indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (deduplicate_items = value)", "description": ["Controls usage of the B-tree deduplication technique described in Section 65.1.4.3 . Set to ON or OFF to enable or disable the optimization. (Alternative spellings of ON and OFF are allowed as described in Section 19.1 .) The default is ON .", "Turning deduplicate_items off via ALTER INDEX prevents future insertions from triggering deduplication, but does not in itself make existing posting list tuples use the standard tuple representation."]}}, "content_hash": "0018bd74bc3d727424a231c2acf03e6bc8711a92ae1496cd00ce39534ee05a4f", "imported_at": "2026-09-27T09:57:58.907", "url": "/wiki/relopts/btree-deduplicate-items/?v=18", "cells": [{"major": "10", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 10.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/btree-deduplicate-items/?v=10"}, {"major": "11", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 11.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/btree-deduplicate-items/?v=11"}, {"major": "12", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 12.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/btree-deduplicate-items/?v=12"}, {"major": "13", "state": "added", "label": "First recorded in this sample", "title": "PostgreSQL 13.23 \u00b7 First recorded in this sample", "url": "/wiki/relopts/btree-deduplicate-items/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/btree-deduplicate-items/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/btree-deduplicate-items/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/btree-deduplicate-items/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/btree-deduplicate-items/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/btree-deduplicate-items/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/btree-deduplicate-items/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/btree-deduplicate-items/?v=20"}], "present": true}, {"slug": "btree-fillfactor", "name": "fillfactor", "name_zh": "B-tree indexes fillfactor", "category": "B-tree indexes", "summary": "Controls how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "aliases": ["btree.fillfactor"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "B-tree indexes"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "90"}, {"label": "Range", "value": "10\u2013100 percent"}], "related": [{"url": "/docs/sql/create-index/?v=10", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS", "path": "sql-createindex.html", "label": "PostgreSQL 10 English manual", "sha256": "7b1817d528a7de6c346b120316ca74abde75ccf0f2f21c34a72dbe032a88e403"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to B-tree indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index build, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to gradual degradation in the index's efficiency. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected. If the table is static then fillfactor 100 is best to minimize the index's physical size, but for heavily updated tables a smaller fillfactor is better to minimize the need for page splits. The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "11": {"facts": [{"label": "Applies to", "value": "B-tree indexes"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "90"}, {"label": "Range", "value": "10\u2013100 percent"}], "related": [{"url": "/docs/sql/create-index/?v=11", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS", "path": "sql-createindex.html", "label": "PostgreSQL 11 English manual", "sha256": "e7cfb07816fa696f1a7d5a3a8c43287796d08f48bddd6b2413279895b57ff2da"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to B-tree indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index build, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to gradual degradation in the index's efficiency. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected. If the table is static then fillfactor 100 is best to minimize the index's physical size, but for heavily updated tables a smaller fillfactor is better to minimize the need for page splits. The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "12": {"facts": [{"label": "Applies to", "value": "B-tree indexes"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "90"}, {"label": "Range", "value": "10\u2013100 percent"}], "related": [{"url": "/docs/sql/create-index/?v=12", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 12 English manual", "sha256": "deedeb34af9b62564d13ab2d379b31b19d4de6fb89a0e712826211914a0c5805"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to B-tree indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index build, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to gradual degradation in the index's efficiency. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected. If the table is static then fillfactor 100 is best to minimize the index's physical size, but for heavily updated tables a smaller fillfactor is better to minimize the need for page splits. The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "13": {"facts": [{"label": "Applies to", "value": "B-tree indexes"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "90"}, {"label": "Range", "value": "10\u2013100 percent"}], "related": [{"url": "/docs/sql/create-index/?v=13", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 13 English manual", "sha256": "a02f612ec64fc7396ab65a1ce4458cd6971bbd8715e2465ae3c5927d20af3840"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to B-tree indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index build, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to gradual degradation in the index's efficiency. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected. If the table is static then fillfactor 100 is best to minimize the index's physical size, but for heavily updated tables a smaller fillfactor is better to minimize the need for page splits. The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "14": {"facts": [{"label": "Applies to", "value": "B-tree indexes"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "90"}, {"label": "Range", "value": "10\u2013100 percent"}], "related": [{"url": "/docs/sql/create-index/?v=14", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 14 English manual", "sha256": "f4d42bd08081490a491dc7bf4fa78b2a49da55ebcd0e7f843862548f7c66d70d"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to B-tree indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 64.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "15": {"facts": [{"label": "Applies to", "value": "B-tree indexes"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "90"}, {"label": "Range", "value": "10\u2013100 percent"}], "related": [{"url": "/docs/sql/create-index/?v=15", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 15 English manual", "sha256": "d0c693e7bccb80a261cfefed9f515fd2d24fb49395dfcbd61672d7915fa0666c"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to B-tree indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 67.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "16": {"facts": [{"label": "Applies to", "value": "B-tree indexes"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "90"}, {"label": "Range", "value": "10\u2013100 percent"}], "related": [{"url": "/docs/sql/create-index/?v=16", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 16 English manual", "sha256": "ede5053e24573587783eee1735daf6cba76010c2773f10ad066d8cdaf7073c83"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to B-tree indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 67.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "17": {"facts": [{"label": "Applies to", "value": "B-tree indexes"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "90"}, {"label": "Range", "value": "10\u2013100 percent"}], "related": [{"url": "/docs/sql/create-index/?v=17", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 17 English manual", "sha256": "7fdb46b4a32c524457958417502f4036888552e0577352ee66f107019bbfffd6"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to B-tree indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 64.1.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "18": {"facts": [{"label": "Applies to", "value": "B-tree indexes"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "90"}, {"label": "Range", "value": "10\u2013100 percent"}], "related": [{"url": "/docs/sql/create-index/?v=18", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 18 English manual", "sha256": "6aa00da55815d13d0355dd25cb1cdb603fa36964993f164d1b6f486011282580"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to B-tree indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (fillfactor = value)", "description": ["Controls how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 65.1.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "19": {"facts": [{"label": "Applies to", "value": "B-tree indexes"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "90"}, {"label": "Range", "value": "10\u2013100 percent"}], "related": [{"url": "/docs/sql/create-index/?v=19", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 19 English manual", "sha256": "e90c2051c335f6636fb68f3b03f98c3282445c537c99fd7d2e74e4943662e224"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to B-tree indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (fillfactor = value)", "description": ["Controls how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 65.1.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "20": {"facts": [{"label": "Applies to", "value": "B-tree indexes"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "90"}, {"label": "Range", "value": "10\u2013100 percent"}], "related": [{"url": "/docs/sql/create-index/?v=20", "label": "CREATE INDEX"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 20 English manual", "sha256": "33a4425c008678a8009be08f283f4f536180f45ebf9f6c2183f06daa3cf385d8"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to B-tree indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (fillfactor = value)", "description": ["Controls how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 65.1.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}}, "content_hash": "8dcef5615c2b49219548e0a30687ebf7fe90a9707bbe1d2c7bf95e807faf3a38", "imported_at": "2026-09-27T09:57:58.908", "url": "/wiki/relopts/btree-fillfactor/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/btree-fillfactor/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/btree-fillfactor/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/btree-fillfactor/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/btree-fillfactor/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/btree-fillfactor/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/btree-fillfactor/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/btree-fillfactor/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/btree-fillfactor/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/btree-fillfactor/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/btree-fillfactor/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/btree-fillfactor/?v=20"}], "present": true}, {"slug": "btree-vacuum-cleanup-index-scale-factor", "name": "vacuum_cleanup_index_scale_factor", "name_zh": "vacuum_cleanup_index_scale_factor", "category": "B-tree indexes", "summary": "Not recorded in the selected version.", "aliases": ["btree.vacuum_cleanup_index_scale_factor"], "versions": {"11": {"facts": [{"label": "Applies to", "value": "B-tree indexes"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/vacuum_cleanup_index_scale_factor/?v=11", "label": "Global parameter vacuum_cleanup_index_scale_factor"}, {"url": "/docs/sql/create-index/?v=11", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS", "path": "sql-createindex.html", "label": "PostgreSQL 11 English manual", "sha256": "e7cfb07816fa696f1a7d5a3a8c43287796d08f48bddd6b2413279895b57ff2da"}, {"url": "/docs/11/runtime-config-client.html#GUC-VACUUM-CLEANUP-INDEX-SCALE-FACTOR", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_cleanup_index_scale_factor", "sha256": "488947b3f6c09ac9a815b8602e852239936b403ef214249fee7aeca1469c25ba"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to B-tree indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}, {"title": "Related global parameter: vacuum_cleanup_index_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the fraction of the total number of heap tuples counted in the previous statistics collection that can be inserted without incurring an index scan at the VACUUM cleanup stage. This setting currently applies to B-tree indexes only.", "If no tuples were deleted from the heap, B-tree indexes are still scanned at the VACUUM cleanup stage when at least one of the following conditions is met: the index statistics are stale, or the index contains deleted pages that can be recycled during cleanup. Index statistics are considered to be stale if the number of newly inserted tuples exceeds the vacuum_cleanup_index_scale_factor fraction of the total number of heap tuples detected by the previous statistics collection. The total number of heap tuples is stored in the index meta-page. Note that the meta-page does not include this data until VACUUM finds no dead tuples, so B-tree index scan at the cleanup stage can only be skipped if the second and subsequent VACUUM cycles detect no dead tuples.", "The value can range from 0 to 10000000000 . When vacuum_cleanup_index_scale_factor is set to 0 , index scans are never skipped during VACUUM cleanup. The default value is 0.1 ."]}], "signature": "WITH (vacuum_cleanup_index_scale_factor = value)", "description": ["Per-index value for vacuum_cleanup_index_scale_factor ."]}, "12": {"facts": [{"label": "Applies to", "value": "B-tree indexes"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/vacuum_cleanup_index_scale_factor/?v=12", "label": "Global parameter vacuum_cleanup_index_scale_factor"}, {"url": "/docs/sql/create-index/?v=12", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createindex.html#INDEX-RELOPTION-VACUUM-CLEANUP-INDEX-SCALE-FACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 12 English manual", "sha256": "deedeb34af9b62564d13ab2d379b31b19d4de6fb89a0e712826211914a0c5805"}, {"url": "/docs/12/runtime-config-client.html#GUC-VACUUM-CLEANUP-INDEX-SCALE-FACTOR", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_cleanup_index_scale_factor", "sha256": "7f27882cdde3b36cef070cdd14ce3f080b65ed837d3f6b41f3faf454ba89cc63"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to B-tree indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}, {"title": "Related global parameter: vacuum_cleanup_index_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the fraction of the total number of heap tuples counted in the previous statistics collection that can be inserted without incurring an index scan at the VACUUM cleanup stage. This setting currently applies to B-tree indexes only.", "If no tuples were deleted from the heap, B-tree indexes are still scanned at the VACUUM cleanup stage when at least one of the following conditions is met: the index statistics are stale, or the index contains deleted pages that can be recycled during cleanup. Index statistics are considered to be stale if the number of newly inserted tuples exceeds the vacuum_cleanup_index_scale_factor fraction of the total number of heap tuples detected by the previous statistics collection. The total number of heap tuples is stored in the index meta-page. Note that the meta-page does not include this data until VACUUM finds no dead tuples, so B-tree index scan at the cleanup stage can only be skipped if the second and subsequent VACUUM cycles detect no dead tuples.", "The value can range from 0 to 10000000000 . When vacuum_cleanup_index_scale_factor is set to 0 , index scans are never skipped during VACUUM cleanup. The default value is 0.1 ."]}], "signature": "WITH (vacuum_cleanup_index_scale_factor = value)", "description": ["Per-index value for vacuum_cleanup_index_scale_factor ."]}}, "content_hash": "0bf23d6fc05faee9928cc742382c6de5275972bda7c761aa87e50b424343dc05", "imported_at": "2026-09-27T09:57:58.910", "url": "/wiki/relopts/btree-vacuum-cleanup-index-scale-factor/?v=18", "cells": [{"major": "10", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 10.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/btree-vacuum-cleanup-index-scale-factor/?v=10"}, {"major": "11", "state": "added", "label": "First recorded in this sample", "title": "PostgreSQL 11.22 \u00b7 First recorded in this sample", "url": "/wiki/relopts/btree-vacuum-cleanup-index-scale-factor/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/btree-vacuum-cleanup-index-scale-factor/?v=12"}, {"major": "13", "state": "removed", "label": "No longer recorded", "title": "PostgreSQL 13.23 \u00b7 No longer recorded", "url": "/wiki/relopts/btree-vacuum-cleanup-index-scale-factor/?v=13"}, {"major": "14", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 14.24 \u00b7 Not recorded in this version", "url": "/wiki/relopts/btree-vacuum-cleanup-index-scale-factor/?v=14"}, {"major": "15", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 15.19 \u00b7 Not recorded in this version", "url": "/wiki/relopts/btree-vacuum-cleanup-index-scale-factor/?v=15"}, {"major": "16", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 16.15 \u00b7 Not recorded in this version", "url": "/wiki/relopts/btree-vacuum-cleanup-index-scale-factor/?v=16"}, {"major": "17", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 17.11 \u00b7 Not recorded in this version", "url": "/wiki/relopts/btree-vacuum-cleanup-index-scale-factor/?v=17"}, {"major": "18", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 18.6 \u00b7 Not recorded in this version", "url": "/wiki/relopts/btree-vacuum-cleanup-index-scale-factor/?v=18"}, {"major": "19", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 19 beta 4 \u00b7 Not recorded in this version", "url": "/wiki/relopts/btree-vacuum-cleanup-index-scale-factor/?v=19"}, {"major": "20", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 20 devel \u00b7 Not recorded in this version", "url": "/wiki/relopts/btree-vacuum-cleanup-index-scale-factor/?v=20"}], "present": false}, {"slug": "brin-autosummarize", "name": "autosummarize", "name_zh": "autosummarize", "category": "BRIN indexes", "summary": "Defines whether a summarization run is queued for the previous page range whenever an insertion is detected on the next one (see Section 65.5.1.1 for more details). The default is off .", "aliases": ["brin.autosummarize"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "BRIN indexes"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-index/?v=10", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS", "path": "sql-createindex.html", "label": "PostgreSQL 10 English manual", "sha256": "7b1817d528a7de6c346b120316ca74abde75ccf0f2f21c34a72dbe032a88e403"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to BRIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (autosummarize = value)", "description": ["Defines whether a summarization run is invoked for the previous page range whenever an insertion is detected on the next one."]}, "11": {"facts": [{"label": "Applies to", "value": "BRIN indexes"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-index/?v=11", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS", "path": "sql-createindex.html", "label": "PostgreSQL 11 English manual", "sha256": "e7cfb07816fa696f1a7d5a3a8c43287796d08f48bddd6b2413279895b57ff2da"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to BRIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (autosummarize = value)", "description": ["Defines whether a summarization run is invoked for the previous page range whenever an insertion is detected on the next one."]}, "12": {"facts": [{"label": "Applies to", "value": "BRIN indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "off"}], "related": [{"url": "/docs/sql/create-index/?v=12", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createindex.html#INDEX-RELOPTION-AUTOSUMMARIZE", "path": "sql-createindex.html", "label": "PostgreSQL 12 English manual", "sha256": "deedeb34af9b62564d13ab2d379b31b19d4de6fb89a0e712826211914a0c5805"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to BRIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (autosummarize = value)", "description": ["Defines whether a summarization run is queued for the previous page range whenever an insertion is detected on the next one. See Section 67.1.1 for more details. The default is off ."]}, "13": {"facts": [{"label": "Applies to", "value": "BRIN indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "off"}], "related": [{"url": "/docs/sql/create-index/?v=13", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createindex.html#INDEX-RELOPTION-AUTOSUMMARIZE", "path": "sql-createindex.html", "label": "PostgreSQL 13 English manual", "sha256": "a02f612ec64fc7396ab65a1ce4458cd6971bbd8715e2465ae3c5927d20af3840"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to BRIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (autosummarize = value)", "description": ["Defines whether a summarization run is queued for the previous page range whenever an insertion is detected on the next one. See Section 67.1.1 for more details. The default is off ."]}, "14": {"facts": [{"label": "Applies to", "value": "BRIN indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "off"}], "related": [{"url": "/docs/sql/create-index/?v=14", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createindex.html#INDEX-RELOPTION-AUTOSUMMARIZE", "path": "sql-createindex.html", "label": "PostgreSQL 14 English manual", "sha256": "f4d42bd08081490a491dc7bf4fa78b2a49da55ebcd0e7f843862548f7c66d70d"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to BRIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (autosummarize = value)", "description": ["Defines whether a summarization run is queued for the previous page range whenever an insertion is detected on the next one. See Section 68.1.1 for more details. The default is off ."]}, "15": {"facts": [{"label": "Applies to", "value": "BRIN indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "off"}], "related": [{"url": "/docs/sql/create-index/?v=15", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createindex.html#INDEX-RELOPTION-AUTOSUMMARIZE", "path": "sql-createindex.html", "label": "PostgreSQL 15 English manual", "sha256": "d0c693e7bccb80a261cfefed9f515fd2d24fb49395dfcbd61672d7915fa0666c"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to BRIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (autosummarize = value)", "description": ["Defines whether a summarization run is queued for the previous page range whenever an insertion is detected on the next one. See Section 71.1.1 for more details. The default is off ."]}, "16": {"facts": [{"label": "Applies to", "value": "BRIN indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "off"}], "related": [{"url": "/docs/sql/create-index/?v=16", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createindex.html#INDEX-RELOPTION-AUTOSUMMARIZE", "path": "sql-createindex.html", "label": "PostgreSQL 16 English manual", "sha256": "ede5053e24573587783eee1735daf6cba76010c2773f10ad066d8cdaf7073c83"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to BRIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (autosummarize = value)", "description": ["Defines whether a summarization run is queued for the previous page range whenever an insertion is detected on the next one. See Section 71.1.1 for more details. The default is off ."]}, "17": {"facts": [{"label": "Applies to", "value": "BRIN indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "off"}], "related": [{"url": "/docs/sql/create-index/?v=17", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createindex.html#INDEX-RELOPTION-AUTOSUMMARIZE", "path": "sql-createindex.html", "label": "PostgreSQL 17 English manual", "sha256": "7fdb46b4a32c524457958417502f4036888552e0577352ee66f107019bbfffd6"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to BRIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (autosummarize = value)", "description": ["Defines whether a summarization run is queued for the previous page range whenever an insertion is detected on the next one. See Section 64.5.1.1 for more details. The default is off ."]}, "18": {"facts": [{"label": "Applies to", "value": "BRIN indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "off"}], "related": [{"url": "/docs/sql/create-index/?v=18", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createindex.html#INDEX-RELOPTION-AUTOSUMMARIZE", "path": "sql-createindex.html", "label": "PostgreSQL 18 English manual", "sha256": "6aa00da55815d13d0355dd25cb1cdb603fa36964993f164d1b6f486011282580"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to BRIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (autosummarize = value)", "description": ["Defines whether a summarization run is queued for the previous page range whenever an insertion is detected on the next one (see Section 65.5.1.1 for more details). The default is off ."]}, "19": {"facts": [{"label": "Applies to", "value": "BRIN indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "off"}], "related": [{"url": "/docs/sql/create-index/?v=19", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createindex.html#INDEX-RELOPTION-AUTOSUMMARIZE", "path": "sql-createindex.html", "label": "PostgreSQL 19 English manual", "sha256": "e90c2051c335f6636fb68f3b03f98c3282445c537c99fd7d2e74e4943662e224"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to BRIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (autosummarize = value)", "description": ["Defines whether a summarization run is queued for the previous page range whenever an insertion is detected on the next one (see Section 65.5.1.1 for more details). The default is off ."]}, "20": {"facts": [{"label": "Applies to", "value": "BRIN indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "off"}], "related": [{"url": "/docs/sql/create-index/?v=20", "label": "CREATE INDEX"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createindex.html#INDEX-RELOPTION-AUTOSUMMARIZE", "path": "sql-createindex.html", "label": "PostgreSQL 20 English manual", "sha256": "33a4425c008678a8009be08f283f4f536180f45ebf9f6c2183f06daa3cf385d8"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to BRIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (autosummarize = value)", "description": ["Defines whether a summarization run is queued for the previous page range whenever an insertion is detected on the next one (see Section 65.5.1.1 for more details). The default is off ."]}}, "content_hash": "8835f61ad44661207f06788526607ec03c128b49e96c2aead759a145338f4449", "imported_at": "2026-09-27T09:57:58.902", "url": "/wiki/relopts/brin-autosummarize/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/brin-autosummarize/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/brin-autosummarize/?v=11"}, {"major": "12", "state": "changed", "label": "Interface or attribute change", "title": "PostgreSQL 12.22 \u00b7 Interface or attribute change", "url": "/wiki/relopts/brin-autosummarize/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/brin-autosummarize/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/brin-autosummarize/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/brin-autosummarize/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/brin-autosummarize/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/brin-autosummarize/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/brin-autosummarize/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/brin-autosummarize/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/brin-autosummarize/?v=20"}], "present": true}, {"slug": "brin-pages-per-range", "name": "pages_per_range", "name_zh": "pages_per_range", "category": "BRIN indexes", "summary": "Defines the number of table blocks that make up one block range for each entry of a BRIN index (see Section 65.5.1 for more details). The default is 128 .", "aliases": ["brin.pages_per_range"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "BRIN indexes"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "128"}], "related": [{"url": "/docs/sql/create-index/?v=10", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS", "path": "sql-createindex.html", "label": "PostgreSQL 10 English manual", "sha256": "7b1817d528a7de6c346b120316ca74abde75ccf0f2f21c34a72dbe032a88e403"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to BRIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (pages_per_range = value)", "description": ["Defines the number of table blocks that make up one block range for each entry of a BRIN index (see Section 65.1 for more details). The default is 128 ."]}, "11": {"facts": [{"label": "Applies to", "value": "BRIN indexes"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "128"}], "related": [{"url": "/docs/sql/create-index/?v=11", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS", "path": "sql-createindex.html", "label": "PostgreSQL 11 English manual", "sha256": "e7cfb07816fa696f1a7d5a3a8c43287796d08f48bddd6b2413279895b57ff2da"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to BRIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (pages_per_range = value)", "description": ["Defines the number of table blocks that make up one block range for each entry of a BRIN index (see Section 67.1 for more details). The default is 128 ."]}, "12": {"facts": [{"label": "Applies to", "value": "BRIN indexes"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "128"}], "related": [{"url": "/docs/sql/create-index/?v=12", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createindex.html#INDEX-RELOPTION-PAGES-PER-RANGE", "path": "sql-createindex.html", "label": "PostgreSQL 12 English manual", "sha256": "deedeb34af9b62564d13ab2d379b31b19d4de6fb89a0e712826211914a0c5805"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to BRIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (pages_per_range = value)", "description": ["Defines the number of table blocks that make up one block range for each entry of a BRIN index (see Section 67.1 for more details). The default is 128 ."]}, "13": {"facts": [{"label": "Applies to", "value": "BRIN indexes"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "128"}], "related": [{"url": "/docs/sql/create-index/?v=13", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createindex.html#INDEX-RELOPTION-PAGES-PER-RANGE", "path": "sql-createindex.html", "label": "PostgreSQL 13 English manual", "sha256": "a02f612ec64fc7396ab65a1ce4458cd6971bbd8715e2465ae3c5927d20af3840"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to BRIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (pages_per_range = value)", "description": ["Defines the number of table blocks that make up one block range for each entry of a BRIN index (see Section 67.1 for more details). The default is 128 ."]}, "14": {"facts": [{"label": "Applies to", "value": "BRIN indexes"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "128"}], "related": [{"url": "/docs/sql/create-index/?v=14", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createindex.html#INDEX-RELOPTION-PAGES-PER-RANGE", "path": "sql-createindex.html", "label": "PostgreSQL 14 English manual", "sha256": "f4d42bd08081490a491dc7bf4fa78b2a49da55ebcd0e7f843862548f7c66d70d"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to BRIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (pages_per_range = value)", "description": ["Defines the number of table blocks that make up one block range for each entry of a BRIN index (see Section 68.1 for more details). The default is 128 ."]}, "15": {"facts": [{"label": "Applies to", "value": "BRIN indexes"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "128"}], "related": [{"url": "/docs/sql/create-index/?v=15", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createindex.html#INDEX-RELOPTION-PAGES-PER-RANGE", "path": "sql-createindex.html", "label": "PostgreSQL 15 English manual", "sha256": "d0c693e7bccb80a261cfefed9f515fd2d24fb49395dfcbd61672d7915fa0666c"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to BRIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (pages_per_range = value)", "description": ["Defines the number of table blocks that make up one block range for each entry of a BRIN index (see Section 71.1 for more details). The default is 128 ."]}, "16": {"facts": [{"label": "Applies to", "value": "BRIN indexes"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "128"}], "related": [{"url": "/docs/sql/create-index/?v=16", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createindex.html#INDEX-RELOPTION-PAGES-PER-RANGE", "path": "sql-createindex.html", "label": "PostgreSQL 16 English manual", "sha256": "ede5053e24573587783eee1735daf6cba76010c2773f10ad066d8cdaf7073c83"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to BRIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (pages_per_range = value)", "description": ["Defines the number of table blocks that make up one block range for each entry of a BRIN index (see Section 71.1 for more details). The default is 128 ."]}, "17": {"facts": [{"label": "Applies to", "value": "BRIN indexes"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "128"}], "related": [{"url": "/docs/sql/create-index/?v=17", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createindex.html#INDEX-RELOPTION-PAGES-PER-RANGE", "path": "sql-createindex.html", "label": "PostgreSQL 17 English manual", "sha256": "7fdb46b4a32c524457958417502f4036888552e0577352ee66f107019bbfffd6"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to BRIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (pages_per_range = value)", "description": ["Defines the number of table blocks that make up one block range for each entry of a BRIN index (see Section 64.5.1 for more details). The default is 128 ."]}, "18": {"facts": [{"label": "Applies to", "value": "BRIN indexes"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "128"}], "related": [{"url": "/docs/sql/create-index/?v=18", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createindex.html#INDEX-RELOPTION-PAGES-PER-RANGE", "path": "sql-createindex.html", "label": "PostgreSQL 18 English manual", "sha256": "6aa00da55815d13d0355dd25cb1cdb603fa36964993f164d1b6f486011282580"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to BRIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (pages_per_range = value)", "description": ["Defines the number of table blocks that make up one block range for each entry of a BRIN index (see Section 65.5.1 for more details). The default is 128 ."]}, "19": {"facts": [{"label": "Applies to", "value": "BRIN indexes"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "128"}], "related": [{"url": "/docs/sql/create-index/?v=19", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createindex.html#INDEX-RELOPTION-PAGES-PER-RANGE", "path": "sql-createindex.html", "label": "PostgreSQL 19 English manual", "sha256": "e90c2051c335f6636fb68f3b03f98c3282445c537c99fd7d2e74e4943662e224"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to BRIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (pages_per_range = value)", "description": ["Defines the number of table blocks that make up one block range for each entry of a BRIN index (see Section 65.5.1 for more details). The default is 128 ."]}, "20": {"facts": [{"label": "Applies to", "value": "BRIN indexes"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "128"}], "related": [{"url": "/docs/sql/create-index/?v=20", "label": "CREATE INDEX"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createindex.html#INDEX-RELOPTION-PAGES-PER-RANGE", "path": "sql-createindex.html", "label": "PostgreSQL 20 English manual", "sha256": "33a4425c008678a8009be08f283f4f536180f45ebf9f6c2183f06daa3cf385d8"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to BRIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (pages_per_range = value)", "description": ["Defines the number of table blocks that make up one block range for each entry of a BRIN index (see Section 65.5.1 for more details). The default is 128 ."]}}, "content_hash": "b2e9b7720f4c0def0fac5f90dd1f279e1173c10acaf5996d7c7f3e5a7357b5f1", "imported_at": "2026-09-27T09:57:58.905", "url": "/wiki/relopts/brin-pages-per-range/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/brin-pages-per-range/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/brin-pages-per-range/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/brin-pages-per-range/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/brin-pages-per-range/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/brin-pages-per-range/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/brin-pages-per-range/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/brin-pages-per-range/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/brin-pages-per-range/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/brin-pages-per-range/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/brin-pages-per-range/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/brin-pages-per-range/?v=20"}], "present": true}, {"slug": "gin-fastupdate", "name": "fastupdate", "name_zh": "fastupdate", "category": "GIN indexes", "summary": "Controls usage of the fast update technique described in Section 65.4.4.1 . ON enables fast update, OFF disables it. The default is ON .", "aliases": ["gin.fastupdate"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "GIN indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "ON"}], "related": [{"url": "/docs/sql/create-index/?v=10", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS", "path": "sql-createindex.html", "label": "PostgreSQL 10 English manual", "sha256": "7b1817d528a7de6c346b120316ca74abde75ccf0f2f21c34a72dbe032a88e403"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (fastupdate = value)", "description": ["This setting controls usage of the fast update technique described in Section 64.4.1 . It is a Boolean parameter: ON enables fast update, OFF disables it. (Alternative spellings of ON and OFF are allowed as described in Section 19.1 .) The default is ON .", "Turning fastupdate off via ALTER INDEX prevents future insertions from going into the list of pending index entries, but does not in itself flush previous entries. You might want to VACUUM the table or call gin_clean_pending_list function afterward to ensure the pending list is emptied."]}, "11": {"facts": [{"label": "Applies to", "value": "GIN indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "ON"}], "related": [{"url": "/docs/sql/create-index/?v=11", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS", "path": "sql-createindex.html", "label": "PostgreSQL 11 English manual", "sha256": "e7cfb07816fa696f1a7d5a3a8c43287796d08f48bddd6b2413279895b57ff2da"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (fastupdate = value)", "description": ["This setting controls usage of the fast update technique described in Section 66.4.1 . It is a Boolean parameter: ON enables fast update, OFF disables it. (Alternative spellings of ON and OFF are allowed as described in Section 19.1 .) The default is ON .", "Turning fastupdate off via ALTER INDEX prevents future insertions from going into the list of pending index entries, but does not in itself flush previous entries. You might want to VACUUM the table or call gin_clean_pending_list function afterward to ensure the pending list is emptied."]}, "12": {"facts": [{"label": "Applies to", "value": "GIN indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "ON"}], "related": [{"url": "/docs/sql/create-index/?v=12", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createindex.html#INDEX-RELOPTION-FASTUPDATE", "path": "sql-createindex.html", "label": "PostgreSQL 12 English manual", "sha256": "deedeb34af9b62564d13ab2d379b31b19d4de6fb89a0e712826211914a0c5805"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (fastupdate = value)", "description": ["This setting controls usage of the fast update technique described in Section 66.4.1 . It is a Boolean parameter: ON enables fast update, OFF disables it. (Alternative spellings of ON and OFF are allowed as described in Section 19.1 .) The default is ON .", "Turning fastupdate off via ALTER INDEX prevents future insertions from going into the list of pending index entries, but does not in itself flush previous entries. You might want to VACUUM the table or call gin_clean_pending_list function afterward to ensure the pending list is emptied."]}, "13": {"facts": [{"label": "Applies to", "value": "GIN indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "ON"}], "related": [{"url": "/docs/sql/create-index/?v=13", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createindex.html#INDEX-RELOPTION-FASTUPDATE", "path": "sql-createindex.html", "label": "PostgreSQL 13 English manual", "sha256": "a02f612ec64fc7396ab65a1ce4458cd6971bbd8715e2465ae3c5927d20af3840"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (fastupdate = value)", "description": ["This setting controls usage of the fast update technique described in Section 66.4.1 . It is a Boolean parameter: ON enables fast update, OFF disables it. The default is ON .", "Turning fastupdate off via ALTER INDEX prevents future insertions from going into the list of pending index entries, but does not in itself flush previous entries. You might want to VACUUM the table or call gin_clean_pending_list function afterward to ensure the pending list is emptied."]}, "14": {"facts": [{"label": "Applies to", "value": "GIN indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "ON"}], "related": [{"url": "/docs/sql/create-index/?v=14", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createindex.html#INDEX-RELOPTION-FASTUPDATE", "path": "sql-createindex.html", "label": "PostgreSQL 14 English manual", "sha256": "f4d42bd08081490a491dc7bf4fa78b2a49da55ebcd0e7f843862548f7c66d70d"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (fastupdate = value)", "description": ["This setting controls usage of the fast update technique described in Section 67.4.1 . It is a Boolean parameter: ON enables fast update, OFF disables it. The default is ON .", "Turning fastupdate off via ALTER INDEX prevents future insertions from going into the list of pending index entries, but does not in itself flush previous entries. You might want to VACUUM the table or call gin_clean_pending_list function afterward to ensure the pending list is emptied."]}, "15": {"facts": [{"label": "Applies to", "value": "GIN indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "ON"}], "related": [{"url": "/docs/sql/create-index/?v=15", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createindex.html#INDEX-RELOPTION-FASTUPDATE", "path": "sql-createindex.html", "label": "PostgreSQL 15 English manual", "sha256": "d0c693e7bccb80a261cfefed9f515fd2d24fb49395dfcbd61672d7915fa0666c"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (fastupdate = value)", "description": ["This setting controls usage of the fast update technique described in Section 70.4.1 . It is a Boolean parameter: ON enables fast update, OFF disables it. The default is ON .", "Turning fastupdate off via ALTER INDEX prevents future insertions from going into the list of pending index entries, but does not in itself flush previous entries. You might want to VACUUM the table or call gin_clean_pending_list function afterward to ensure the pending list is emptied."]}, "16": {"facts": [{"label": "Applies to", "value": "GIN indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "ON"}], "related": [{"url": "/docs/sql/create-index/?v=16", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createindex.html#INDEX-RELOPTION-FASTUPDATE", "path": "sql-createindex.html", "label": "PostgreSQL 16 English manual", "sha256": "ede5053e24573587783eee1735daf6cba76010c2773f10ad066d8cdaf7073c83"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (fastupdate = value)", "description": ["This setting controls usage of the fast update technique described in Section 70.4.1 . It is a Boolean parameter: ON enables fast update, OFF disables it. The default is ON .", "Turning fastupdate off via ALTER INDEX prevents future insertions from going into the list of pending index entries, but does not in itself flush previous entries. You might want to VACUUM the table or call gin_clean_pending_list function afterward to ensure the pending list is emptied."]}, "17": {"facts": [{"label": "Applies to", "value": "GIN indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "ON"}], "related": [{"url": "/docs/sql/create-index/?v=17", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createindex.html#INDEX-RELOPTION-FASTUPDATE", "path": "sql-createindex.html", "label": "PostgreSQL 17 English manual", "sha256": "7fdb46b4a32c524457958417502f4036888552e0577352ee66f107019bbfffd6"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (fastupdate = value)", "description": ["This setting controls usage of the fast update technique described in Section 64.4.4.1 . It is a Boolean parameter: ON enables fast update, OFF disables it. The default is ON .", "Turning fastupdate off via ALTER INDEX prevents future insertions from going into the list of pending index entries, but does not in itself flush previous entries. You might want to VACUUM the table or call gin_clean_pending_list function afterward to ensure the pending list is emptied."]}, "18": {"facts": [{"label": "Applies to", "value": "GIN indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "ON"}], "related": [{"url": "/docs/sql/create-index/?v=18", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createindex.html#INDEX-RELOPTION-FASTUPDATE", "path": "sql-createindex.html", "label": "PostgreSQL 18 English manual", "sha256": "6aa00da55815d13d0355dd25cb1cdb603fa36964993f164d1b6f486011282580"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (fastupdate = value)", "description": ["Controls usage of the fast update technique described in Section 65.4.4.1 . ON enables fast update, OFF disables it. The default is ON .", "Turning fastupdate off via ALTER INDEX prevents future insertions from going into the list of pending index entries, but does not in itself flush existing entries. You might want to VACUUM the table or call the gin_clean_pending_list function afterward to ensure the pending list is emptied."]}, "19": {"facts": [{"label": "Applies to", "value": "GIN indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "ON"}], "related": [{"url": "/docs/sql/create-index/?v=19", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createindex.html#INDEX-RELOPTION-FASTUPDATE", "path": "sql-createindex.html", "label": "PostgreSQL 19 English manual", "sha256": "e90c2051c335f6636fb68f3b03f98c3282445c537c99fd7d2e74e4943662e224"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (fastupdate = value)", "description": ["Controls usage of the fast update technique described in Section 65.4.4.1 . ON enables fast update, OFF disables it. The default is ON .", "Turning fastupdate off via ALTER INDEX prevents future insertions from going into the list of pending index entries, but does not in itself flush existing entries. You might want to VACUUM the table or call the gin_clean_pending_list function afterward to ensure the pending list is emptied."]}, "20": {"facts": [{"label": "Applies to", "value": "GIN indexes"}, {"label": "Value type", "value": "boolean"}, {"label": "Default", "value": "ON"}], "related": [{"url": "/docs/sql/create-index/?v=20", "label": "CREATE INDEX"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createindex.html#INDEX-RELOPTION-FASTUPDATE", "path": "sql-createindex.html", "label": "PostgreSQL 20 English manual", "sha256": "33a4425c008678a8009be08f283f4f536180f45ebf9f6c2183f06daa3cf385d8"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (fastupdate = value)", "description": ["Controls usage of the fast update technique described in Section 65.4.4.1 . ON enables fast update, OFF disables it. The default is ON .", "Turning fastupdate off via ALTER INDEX prevents future insertions from going into the list of pending index entries, but does not in itself flush existing entries. You might want to VACUUM the table or call the gin_clean_pending_list function afterward to ensure the pending list is emptied."]}}, "content_hash": "a988e39e0e1d82b32ce54db0a681fa0eb486d8e20114c127784fbd4c6dd1b5df", "imported_at": "2026-09-27T09:57:58.912", "url": "/wiki/relopts/gin-fastupdate/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/gin-fastupdate/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/gin-fastupdate/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/gin-fastupdate/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/gin-fastupdate/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/gin-fastupdate/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/gin-fastupdate/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/gin-fastupdate/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/gin-fastupdate/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/gin-fastupdate/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/gin-fastupdate/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/gin-fastupdate/?v=20"}], "present": true}, {"slug": "gin-gin-pending-list-limit", "name": "gin_pending_list_limit", "name_zh": "gin_pending_list_limit", "category": "GIN indexes", "summary": "Overrides the global setting of gin_pending_list_limit for this index. This value is specified in kilobytes.", "aliases": ["gin.gin_pending_list_limit"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "GIN indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/gin_pending_list_limit/?v=10", "label": "Global parameter gin_pending_list_limit"}, {"url": "/docs/sql/create-index/?v=10", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS", "path": "sql-createindex.html", "label": "PostgreSQL 10 English manual", "sha256": "7b1817d528a7de6c346b120316ca74abde75ccf0f2f21c34a72dbe032a88e403"}, {"url": "/docs/10/runtime-config-client.html#GUC-GIN-PENDING-LIST-LIMIT", "path": "runtime-config-client.html", "label": "Related global parameter: gin_pending_list_limit", "sha256": "81c199a46b03a65a060e25cf874fc7ddd28b18261a6472a912954073556935b4"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}, {"title": "Related global parameter: gin_pending_list_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Sets the maximum size of the GIN pending list which is used when fastupdate is enabled. If the list grows larger than this maximum size, it is cleaned up by moving the entries in it to the main GIN data structure in bulk. The default is four megabytes ( 4MB ). This setting can be overridden for individual GIN indexes by changing index storage parameters. See Section 64.4.1 and Section 64.5 for more information."]}], "signature": "WITH (gin_pending_list_limit = value)", "description": ["Custom gin_pending_list_limit parameter. This value is specified in kilobytes."]}, "11": {"facts": [{"label": "Applies to", "value": "GIN indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/gin_pending_list_limit/?v=11", "label": "Global parameter gin_pending_list_limit"}, {"url": "/docs/sql/create-index/?v=11", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS", "path": "sql-createindex.html", "label": "PostgreSQL 11 English manual", "sha256": "e7cfb07816fa696f1a7d5a3a8c43287796d08f48bddd6b2413279895b57ff2da"}, {"url": "/docs/11/runtime-config-client.html#GUC-GIN-PENDING-LIST-LIMIT", "path": "runtime-config-client.html", "label": "Related global parameter: gin_pending_list_limit", "sha256": "488947b3f6c09ac9a815b8602e852239936b403ef214249fee7aeca1469c25ba"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}, {"title": "Related global parameter: gin_pending_list_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Sets the maximum size of the GIN pending list which is used when fastupdate is enabled. If the list grows larger than this maximum size, it is cleaned up by moving the entries in it to the main GIN data structure in bulk. The default is four megabytes ( 4MB ). This setting can be overridden for individual GIN indexes by changing index storage parameters. See Section 66.4.1 and Section 66.5 for more information."]}], "signature": "WITH (gin_pending_list_limit = value)", "description": ["Custom gin_pending_list_limit parameter. This value is specified in kilobytes."]}, "12": {"facts": [{"label": "Applies to", "value": "GIN indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/gin_pending_list_limit/?v=12", "label": "Global parameter gin_pending_list_limit"}, {"url": "/docs/sql/create-index/?v=12", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createindex.html#INDEX-RELOPTION-GIN-PENDING-LIST-LIMIT", "path": "sql-createindex.html", "label": "PostgreSQL 12 English manual", "sha256": "deedeb34af9b62564d13ab2d379b31b19d4de6fb89a0e712826211914a0c5805"}, {"url": "/docs/12/runtime-config-client.html#GUC-GIN-PENDING-LIST-LIMIT", "path": "runtime-config-client.html", "label": "Related global parameter: gin_pending_list_limit", "sha256": "7f27882cdde3b36cef070cdd14ce3f080b65ed837d3f6b41f3faf454ba89cc63"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}, {"title": "Related global parameter: gin_pending_list_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Sets the maximum size of a GIN index's pending list, which is used when fastupdate is enabled. If the list grows larger than this maximum size, it is cleaned up by moving the entries in it to the index's main GIN data structure in bulk. If this value is specified without units, it is taken as kilobytes. The default is four megabytes ( 4MB ). This setting can be overridden for individual GIN indexes by changing index storage parameters. See Section 66.4.1 and Section 66.5 for more information."]}], "signature": "WITH (gin_pending_list_limit = value)", "description": ["Custom gin_pending_list_limit parameter. This value is specified in kilobytes."]}, "13": {"facts": [{"label": "Applies to", "value": "GIN indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/gin_pending_list_limit/?v=13", "label": "Global parameter gin_pending_list_limit"}, {"url": "/docs/sql/create-index/?v=13", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createindex.html#INDEX-RELOPTION-GIN-PENDING-LIST-LIMIT", "path": "sql-createindex.html", "label": "PostgreSQL 13 English manual", "sha256": "a02f612ec64fc7396ab65a1ce4458cd6971bbd8715e2465ae3c5927d20af3840"}, {"url": "/docs/13/runtime-config-client.html#GUC-GIN-PENDING-LIST-LIMIT", "path": "runtime-config-client.html", "label": "Related global parameter: gin_pending_list_limit", "sha256": "5d70022f2524a39e7c5745698de51d867f687c70394779ad154e05648e923c7d"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}, {"title": "Related global parameter: gin_pending_list_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Sets the maximum size of a GIN index's pending list, which is used when fastupdate is enabled. If the list grows larger than this maximum size, it is cleaned up by moving the entries in it to the index's main GIN data structure in bulk. If this value is specified without units, it is taken as kilobytes. The default is four megabytes ( 4MB ). This setting can be overridden for individual GIN indexes by changing index storage parameters. See Section 66.4.1 and Section 66.5 for more information."]}], "signature": "WITH (gin_pending_list_limit = value)", "description": ["Custom gin_pending_list_limit parameter. This value is specified in kilobytes."]}, "14": {"facts": [{"label": "Applies to", "value": "GIN indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/gin_pending_list_limit/?v=14", "label": "Global parameter gin_pending_list_limit"}, {"url": "/docs/sql/create-index/?v=14", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createindex.html#INDEX-RELOPTION-GIN-PENDING-LIST-LIMIT", "path": "sql-createindex.html", "label": "PostgreSQL 14 English manual", "sha256": "f4d42bd08081490a491dc7bf4fa78b2a49da55ebcd0e7f843862548f7c66d70d"}, {"url": "/docs/14/runtime-config-client.html#GUC-GIN-PENDING-LIST-LIMIT", "path": "runtime-config-client.html", "label": "Related global parameter: gin_pending_list_limit", "sha256": "35d48bb20f151039202a7cafbe7c4ffb109262110d62b2ab75844a3d80c2cebb"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}, {"title": "Related global parameter: gin_pending_list_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Sets the maximum size of a GIN index's pending list, which is used when fastupdate is enabled. If the list grows larger than this maximum size, it is cleaned up by moving the entries in it to the index's main GIN data structure in bulk. If this value is specified without units, it is taken as kilobytes. The default is four megabytes ( 4MB ). This setting can be overridden for individual GIN indexes by changing index storage parameters. See Section 67.4.1 and Section 67.5 for more information."]}], "signature": "WITH (gin_pending_list_limit = value)", "description": ["Custom gin_pending_list_limit parameter. This value is specified in kilobytes."]}, "15": {"facts": [{"label": "Applies to", "value": "GIN indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/gin_pending_list_limit/?v=15", "label": "Global parameter gin_pending_list_limit"}, {"url": "/docs/sql/create-index/?v=15", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createindex.html#INDEX-RELOPTION-GIN-PENDING-LIST-LIMIT", "path": "sql-createindex.html", "label": "PostgreSQL 15 English manual", "sha256": "d0c693e7bccb80a261cfefed9f515fd2d24fb49395dfcbd61672d7915fa0666c"}, {"url": "/docs/15/runtime-config-client.html#GUC-GIN-PENDING-LIST-LIMIT", "path": "runtime-config-client.html", "label": "Related global parameter: gin_pending_list_limit", "sha256": "fdcf588ddeeac62758840aa3b8d6ead7e37e1b0c72795e339f67db5b23509462"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}, {"title": "Related global parameter: gin_pending_list_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Sets the maximum size of a GIN index's pending list, which is used when fastupdate is enabled. If the list grows larger than this maximum size, it is cleaned up by moving the entries in it to the index's main GIN data structure in bulk. If this value is specified without units, it is taken as kilobytes. The default is four megabytes ( 4MB ). This setting can be overridden for individual GIN indexes by changing index storage parameters. See Section 70.4.1 and Section 70.5 for more information."]}], "signature": "WITH (gin_pending_list_limit = value)", "description": ["Custom gin_pending_list_limit parameter. This value is specified in kilobytes."]}, "16": {"facts": [{"label": "Applies to", "value": "GIN indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/gin_pending_list_limit/?v=16", "label": "Global parameter gin_pending_list_limit"}, {"url": "/docs/sql/create-index/?v=16", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createindex.html#INDEX-RELOPTION-GIN-PENDING-LIST-LIMIT", "path": "sql-createindex.html", "label": "PostgreSQL 16 English manual", "sha256": "ede5053e24573587783eee1735daf6cba76010c2773f10ad066d8cdaf7073c83"}, {"url": "/docs/16/runtime-config-client.html#GUC-GIN-PENDING-LIST-LIMIT", "path": "runtime-config-client.html", "label": "Related global parameter: gin_pending_list_limit", "sha256": "e7e096464bd87b0bfc06652cdbbdd175f7a0e955207580049eae2ee394566b20"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}, {"title": "Related global parameter: gin_pending_list_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Sets the maximum size of a GIN index's pending list, which is used when fastupdate is enabled. If the list grows larger than this maximum size, it is cleaned up by moving the entries in it to the index's main GIN data structure in bulk. If this value is specified without units, it is taken as kilobytes. The default is four megabytes ( 4MB ). This setting can be overridden for individual GIN indexes by changing index storage parameters. See Section 70.4.1 and Section 70.5 for more information."]}], "signature": "WITH (gin_pending_list_limit = value)", "description": ["Custom gin_pending_list_limit parameter. This value is specified in kilobytes."]}, "17": {"facts": [{"label": "Applies to", "value": "GIN indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/gin_pending_list_limit/?v=17", "label": "Global parameter gin_pending_list_limit"}, {"url": "/docs/sql/create-index/?v=17", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createindex.html#INDEX-RELOPTION-GIN-PENDING-LIST-LIMIT", "path": "sql-createindex.html", "label": "PostgreSQL 17 English manual", "sha256": "7fdb46b4a32c524457958417502f4036888552e0577352ee66f107019bbfffd6"}, {"url": "/docs/17/runtime-config-client.html#GUC-GIN-PENDING-LIST-LIMIT", "path": "runtime-config-client.html", "label": "Related global parameter: gin_pending_list_limit", "sha256": "e7ba41a33997d251c23f06ccf17978bf1481db92a2c607026f59af86c25d6f50"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}, {"title": "Related global parameter: gin_pending_list_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Sets the maximum size of a GIN index's pending list, which is used when fastupdate is enabled. If the list grows larger than this maximum size, it is cleaned up by moving the entries in it to the index's main GIN data structure in bulk. If this value is specified without units, it is taken as kilobytes. The default is four megabytes ( 4MB ). This setting can be overridden for individual GIN indexes by changing index storage parameters. See Section 64.4.4.1 and Section 64.4.5 for more information."]}], "signature": "WITH (gin_pending_list_limit = value)", "description": ["Custom gin_pending_list_limit parameter. This value is specified in kilobytes."]}, "18": {"facts": [{"label": "Applies to", "value": "GIN indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/gin_pending_list_limit/?v=18", "label": "Global parameter gin_pending_list_limit"}, {"url": "/docs/sql/create-index/?v=18", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createindex.html#INDEX-RELOPTION-GIN-PENDING-LIST-LIMIT", "path": "sql-createindex.html", "label": "PostgreSQL 18 English manual", "sha256": "6aa00da55815d13d0355dd25cb1cdb603fa36964993f164d1b6f486011282580"}, {"url": "/docs/18/runtime-config-client.html#GUC-GIN-PENDING-LIST-LIMIT", "path": "runtime-config-client.html", "label": "Related global parameter: gin_pending_list_limit", "sha256": "6be6cc70f29eca4695dc43b2b2b94c75b7e0eaaa2c00273d7a98488917a7edb7"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}, {"title": "Related global parameter: gin_pending_list_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Sets the maximum size of a GIN index's pending list, which is used when fastupdate is enabled. If the list grows larger than this maximum size, it is cleaned up by moving the entries in it to the index's main GIN data structure in bulk. If this value is specified without units, it is taken as kilobytes. The default is four megabytes ( 4MB ). This setting can be overridden for individual GIN indexes by changing index storage parameters. See Section 65.4.4.1 and Section 65.4.5 for more information."]}], "signature": "WITH (gin_pending_list_limit = value)", "description": ["Overrides the global setting of gin_pending_list_limit for this index. This value is specified in kilobytes."]}, "19": {"facts": [{"label": "Applies to", "value": "GIN indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/gin_pending_list_limit/?v=19", "label": "Global parameter gin_pending_list_limit"}, {"url": "/docs/sql/create-index/?v=19", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createindex.html#INDEX-RELOPTION-GIN-PENDING-LIST-LIMIT", "path": "sql-createindex.html", "label": "PostgreSQL 19 English manual", "sha256": "e90c2051c335f6636fb68f3b03f98c3282445c537c99fd7d2e74e4943662e224"}, {"url": "/docs/19/runtime-config-client.html#GUC-GIN-PENDING-LIST-LIMIT", "path": "runtime-config-client.html", "label": "Related global parameter: gin_pending_list_limit", "sha256": "b79c9c91df3fa9d8437437c94fbc2054f3b2f320f731c82bf7f8fdc1f326ccaa"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}, {"title": "Related global parameter: gin_pending_list_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Sets the maximum size of a GIN index's pending list, which is used when fastupdate is enabled. If the list grows larger than this maximum size, it is cleaned up by moving the entries in it to the index's main GIN data structure in bulk. If this value is specified without units, it is taken as kilobytes. The default is four megabytes ( 4MB ). This setting can be overridden for individual GIN indexes by changing index storage parameters. See Section 65.4.4.1 and Section 65.4.5 for more information."]}], "signature": "WITH (gin_pending_list_limit = value)", "description": ["Overrides the global setting of gin_pending_list_limit for this index. This value is specified in kilobytes."]}, "20": {"facts": [{"label": "Applies to", "value": "GIN indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/gin_pending_list_limit/?v=20", "label": "Global parameter gin_pending_list_limit"}, {"url": "/docs/sql/create-index/?v=20", "label": "CREATE INDEX"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createindex.html#INDEX-RELOPTION-GIN-PENDING-LIST-LIMIT", "path": "sql-createindex.html", "label": "PostgreSQL 20 English manual", "sha256": "33a4425c008678a8009be08f283f4f536180f45ebf9f6c2183f06daa3cf385d8"}, {"url": "/docs/devel/runtime-config-client.html#GUC-GIN-PENDING-LIST-LIMIT", "path": "runtime-config-client.html", "label": "Related global parameter: gin_pending_list_limit", "sha256": "bd85c6b5d862762e0a876bed529cf5aca7cfd6c45dd8476b5bd44889fde1c6a4"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GIN indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}, {"title": "Related global parameter: gin_pending_list_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Sets the maximum size of a GIN index's pending list, which is used when fastupdate is enabled. If the list grows larger than this maximum size, it is cleaned up by moving the entries in it to the index's main GIN data structure in bulk. If this value is specified without units, it is taken as kilobytes. The default is four megabytes ( 4MB ). This setting can be overridden for individual GIN indexes by changing index storage parameters. See Section 65.4.4.1 and Section 65.4.5 for more information."]}], "signature": "WITH (gin_pending_list_limit = value)", "description": ["Overrides the global setting of gin_pending_list_limit for this index. This value is specified in kilobytes."]}}, "content_hash": "55dab5cd63c99514f82d4a91c0ed7386003d3eb53a7e9000728decc0703dd314", "imported_at": "2026-09-27T09:57:58.914", "url": "/wiki/relopts/gin-gin-pending-list-limit/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/gin-gin-pending-list-limit/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/gin-gin-pending-list-limit/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/gin-gin-pending-list-limit/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/gin-gin-pending-list-limit/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/gin-gin-pending-list-limit/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/gin-gin-pending-list-limit/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/gin-gin-pending-list-limit/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/gin-gin-pending-list-limit/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/gin-gin-pending-list-limit/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/gin-gin-pending-list-limit/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/gin-gin-pending-list-limit/?v=20"}], "present": true}, {"slug": "gist-buffering", "name": "buffering", "name_zh": "buffering", "category": "GiST indexes", "summary": "Controls whether the buffered build technique described in Section 65.2.4.1 is used to build the index. With OFF buffering is disabled, with ON it is enabled, and with AUTO it is initially disabled, but is turned on on-the-fly once the index size reaches effective_cache_size . The default is AUTO . Note that if sorted build is possible, it will be used instead of buffered build unless buffering=ON is specified.", "aliases": ["gist.buffering"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "GiST indexes"}, {"label": "Value type", "value": "enum"}, {"label": "Default", "value": "AUTO"}], "related": [{"url": "/docs/sql/create-index/?v=10", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS", "path": "sql-createindex.html", "label": "PostgreSQL 10 English manual", "sha256": "7b1817d528a7de6c346b120316ca74abde75ccf0f2f21c34a72dbe032a88e403"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (buffering = value)", "description": ["Determines whether the buffering build technique described in Section 62.4.1 is used to build the index. With OFF it is disabled, with ON it is enabled, and with AUTO it is initially disabled, but turned on on-the-fly once the index size reaches effective_cache_size . The default is AUTO ."]}, "11": {"facts": [{"label": "Applies to", "value": "GiST indexes"}, {"label": "Value type", "value": "enum"}, {"label": "Default", "value": "AUTO"}], "related": [{"url": "/docs/sql/create-index/?v=11", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS", "path": "sql-createindex.html", "label": "PostgreSQL 11 English manual", "sha256": "e7cfb07816fa696f1a7d5a3a8c43287796d08f48bddd6b2413279895b57ff2da"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (buffering = value)", "description": ["Determines whether the buffering build technique described in Section 64.4.1 is used to build the index. With OFF it is disabled, with ON it is enabled, and with AUTO it is initially disabled, but turned on on-the-fly once the index size reaches effective_cache_size . The default is AUTO ."]}, "12": {"facts": [{"label": "Applies to", "value": "GiST indexes"}, {"label": "Value type", "value": "enum"}, {"label": "Default", "value": "AUTO"}], "related": [{"url": "/docs/sql/create-index/?v=12", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createindex.html#INDEX-RELOPTION-BUFFERING", "path": "sql-createindex.html", "label": "PostgreSQL 12 English manual", "sha256": "deedeb34af9b62564d13ab2d379b31b19d4de6fb89a0e712826211914a0c5805"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (buffering = value)", "description": ["Determines whether the buffering build technique described in Section 64.4.1 is used to build the index. With OFF it is disabled, with ON it is enabled, and with AUTO it is initially disabled, but turned on on-the-fly once the index size reaches effective_cache_size . The default is AUTO ."]}, "13": {"facts": [{"label": "Applies to", "value": "GiST indexes"}, {"label": "Value type", "value": "enum"}, {"label": "Default", "value": "AUTO"}], "related": [{"url": "/docs/sql/create-index/?v=13", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createindex.html#INDEX-RELOPTION-BUFFERING", "path": "sql-createindex.html", "label": "PostgreSQL 13 English manual", "sha256": "a02f612ec64fc7396ab65a1ce4458cd6971bbd8715e2465ae3c5927d20af3840"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (buffering = value)", "description": ["Determines whether the buffering build technique described in Section 64.4.1 is used to build the index. With OFF it is disabled, with ON it is enabled, and with AUTO it is initially disabled, but turned on on-the-fly once the index size reaches effective_cache_size . The default is AUTO ."]}, "14": {"facts": [{"label": "Applies to", "value": "GiST indexes"}, {"label": "Value type", "value": "enum"}, {"label": "Default", "value": "AUTO"}], "related": [{"url": "/docs/sql/create-index/?v=14", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createindex.html#INDEX-RELOPTION-BUFFERING", "path": "sql-createindex.html", "label": "PostgreSQL 14 English manual", "sha256": "f4d42bd08081490a491dc7bf4fa78b2a49da55ebcd0e7f843862548f7c66d70d"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (buffering = value)", "description": ["Determines whether the buffered build technique described in Section 65.4.1 is used to build the index. With OFF buffering is disabled, with ON it is enabled, and with AUTO it is initially disabled, but is turned on on-the-fly once the index size reaches effective_cache_size . The default is AUTO . Note that if sorted build is possible, it will be used instead of buffered build unless buffering=ON is specified."]}, "15": {"facts": [{"label": "Applies to", "value": "GiST indexes"}, {"label": "Value type", "value": "enum"}, {"label": "Default", "value": "AUTO"}], "related": [{"url": "/docs/sql/create-index/?v=15", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createindex.html#INDEX-RELOPTION-BUFFERING", "path": "sql-createindex.html", "label": "PostgreSQL 15 English manual", "sha256": "d0c693e7bccb80a261cfefed9f515fd2d24fb49395dfcbd61672d7915fa0666c"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (buffering = value)", "description": ["Determines whether the buffered build technique described in Section 68.4.1 is used to build the index. With OFF buffering is disabled, with ON it is enabled, and with AUTO it is initially disabled, but is turned on on-the-fly once the index size reaches effective_cache_size . The default is AUTO . Note that if sorted build is possible, it will be used instead of buffered build unless buffering=ON is specified."]}, "16": {"facts": [{"label": "Applies to", "value": "GiST indexes"}, {"label": "Value type", "value": "enum"}, {"label": "Default", "value": "AUTO"}], "related": [{"url": "/docs/sql/create-index/?v=16", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createindex.html#INDEX-RELOPTION-BUFFERING", "path": "sql-createindex.html", "label": "PostgreSQL 16 English manual", "sha256": "ede5053e24573587783eee1735daf6cba76010c2773f10ad066d8cdaf7073c83"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (buffering = value)", "description": ["Determines whether the buffered build technique described in Section 68.4.1 is used to build the index. With OFF buffering is disabled, with ON it is enabled, and with AUTO it is initially disabled, but is turned on on-the-fly once the index size reaches effective_cache_size . The default is AUTO . Note that if sorted build is possible, it will be used instead of buffered build unless buffering=ON is specified."]}, "17": {"facts": [{"label": "Applies to", "value": "GiST indexes"}, {"label": "Value type", "value": "enum"}, {"label": "Default", "value": "AUTO"}], "related": [{"url": "/docs/sql/create-index/?v=17", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createindex.html#INDEX-RELOPTION-BUFFERING", "path": "sql-createindex.html", "label": "PostgreSQL 17 English manual", "sha256": "7fdb46b4a32c524457958417502f4036888552e0577352ee66f107019bbfffd6"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (buffering = value)", "description": ["Determines whether the buffered build technique described in Section 64.2.4.1 is used to build the index. With OFF buffering is disabled, with ON it is enabled, and with AUTO it is initially disabled, but is turned on on-the-fly once the index size reaches effective_cache_size . The default is AUTO . Note that if sorted build is possible, it will be used instead of buffered build unless buffering=ON is specified."]}, "18": {"facts": [{"label": "Applies to", "value": "GiST indexes"}, {"label": "Value type", "value": "enum"}, {"label": "Default", "value": "AUTO"}], "related": [{"url": "/docs/sql/create-index/?v=18", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createindex.html#INDEX-RELOPTION-BUFFERING", "path": "sql-createindex.html", "label": "PostgreSQL 18 English manual", "sha256": "6aa00da55815d13d0355dd25cb1cdb603fa36964993f164d1b6f486011282580"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (buffering = value)", "description": ["Controls whether the buffered build technique described in Section 65.2.4.1 is used to build the index. With OFF buffering is disabled, with ON it is enabled, and with AUTO it is initially disabled, but is turned on on-the-fly once the index size reaches effective_cache_size . The default is AUTO . Note that if sorted build is possible, it will be used instead of buffered build unless buffering=ON is specified."]}, "19": {"facts": [{"label": "Applies to", "value": "GiST indexes"}, {"label": "Value type", "value": "enum"}, {"label": "Default", "value": "AUTO"}], "related": [{"url": "/docs/sql/create-index/?v=19", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createindex.html#INDEX-RELOPTION-BUFFERING", "path": "sql-createindex.html", "label": "PostgreSQL 19 English manual", "sha256": "e90c2051c335f6636fb68f3b03f98c3282445c537c99fd7d2e74e4943662e224"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (buffering = value)", "description": ["Controls whether the buffered build technique described in Section 65.2.4.1 is used to build the index. With OFF buffering is disabled, with ON it is enabled, and with AUTO it is initially disabled, but is turned on on-the-fly once the index size reaches effective_cache_size . The default is AUTO . Note that if sorted build is possible, it will be used instead of buffered build unless buffering=ON is specified."]}, "20": {"facts": [{"label": "Applies to", "value": "GiST indexes"}, {"label": "Value type", "value": "enum"}, {"label": "Default", "value": "AUTO"}], "related": [{"url": "/docs/sql/create-index/?v=20", "label": "CREATE INDEX"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createindex.html#INDEX-RELOPTION-BUFFERING", "path": "sql-createindex.html", "label": "PostgreSQL 20 English manual", "sha256": "33a4425c008678a8009be08f283f4f536180f45ebf9f6c2183f06daa3cf385d8"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method."]}], "signature": "WITH (buffering = value)", "description": ["Controls whether the buffered build technique described in Section 65.2.4.1 is used to build the index. With OFF buffering is disabled, with ON it is enabled, and with AUTO it is initially disabled, but is turned on on-the-fly once the index size reaches effective_cache_size . The default is AUTO . Note that if sorted build is possible, it will be used instead of buffered build unless buffering=ON is specified."]}}, "content_hash": "b393eaf6e10ec375020a668b1e3954466a4b594c69b49a4c180d1951c793a816", "imported_at": "2026-09-27T09:57:58.915", "url": "/wiki/relopts/gist-buffering/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/gist-buffering/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/gist-buffering/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/gist-buffering/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/gist-buffering/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/gist-buffering/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/gist-buffering/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/gist-buffering/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/gist-buffering/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/gist-buffering/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/gist-buffering/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/gist-buffering/?v=20"}], "present": true}, {"slug": "gist-fillfactor", "name": "fillfactor", "name_zh": "GiST indexes fillfactor", "category": "GiST indexes", "summary": "Controls how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "aliases": ["gist.fillfactor"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "GiST indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=10", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS", "path": "sql-createindex.html", "label": "PostgreSQL 10 English manual", "sha256": "7b1817d528a7de6c346b120316ca74abde75ccf0f2f21c34a72dbe032a88e403"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index build, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to gradual degradation in the index's efficiency. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected. If the table is static then fillfactor 100 is best to minimize the index's physical size, but for heavily updated tables a smaller fillfactor is better to minimize the need for page splits. The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "11": {"facts": [{"label": "Applies to", "value": "GiST indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=11", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS", "path": "sql-createindex.html", "label": "PostgreSQL 11 English manual", "sha256": "e7cfb07816fa696f1a7d5a3a8c43287796d08f48bddd6b2413279895b57ff2da"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index build, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to gradual degradation in the index's efficiency. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected. If the table is static then fillfactor 100 is best to minimize the index's physical size, but for heavily updated tables a smaller fillfactor is better to minimize the need for page splits. The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "12": {"facts": [{"label": "Applies to", "value": "GiST indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=12", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 12 English manual", "sha256": "deedeb34af9b62564d13ab2d379b31b19d4de6fb89a0e712826211914a0c5805"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index build, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to gradual degradation in the index's efficiency. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected. If the table is static then fillfactor 100 is best to minimize the index's physical size, but for heavily updated tables a smaller fillfactor is better to minimize the need for page splits. The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "13": {"facts": [{"label": "Applies to", "value": "GiST indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=13", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 13 English manual", "sha256": "a02f612ec64fc7396ab65a1ce4458cd6971bbd8715e2465ae3c5927d20af3840"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index build, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to gradual degradation in the index's efficiency. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected. If the table is static then fillfactor 100 is best to minimize the index's physical size, but for heavily updated tables a smaller fillfactor is better to minimize the need for page splits. The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "14": {"facts": [{"label": "Applies to", "value": "GiST indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=14", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 14 English manual", "sha256": "f4d42bd08081490a491dc7bf4fa78b2a49da55ebcd0e7f843862548f7c66d70d"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 64.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "15": {"facts": [{"label": "Applies to", "value": "GiST indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=15", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 15 English manual", "sha256": "d0c693e7bccb80a261cfefed9f515fd2d24fb49395dfcbd61672d7915fa0666c"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 67.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "16": {"facts": [{"label": "Applies to", "value": "GiST indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=16", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 16 English manual", "sha256": "ede5053e24573587783eee1735daf6cba76010c2773f10ad066d8cdaf7073c83"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 67.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "17": {"facts": [{"label": "Applies to", "value": "GiST indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=17", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 17 English manual", "sha256": "7fdb46b4a32c524457958417502f4036888552e0577352ee66f107019bbfffd6"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 64.1.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "18": {"facts": [{"label": "Applies to", "value": "GiST indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=18", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 18 English manual", "sha256": "6aa00da55815d13d0355dd25cb1cdb603fa36964993f164d1b6f486011282580"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["Controls how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 65.1.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "19": {"facts": [{"label": "Applies to", "value": "GiST indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=19", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 19 English manual", "sha256": "e90c2051c335f6636fb68f3b03f98c3282445c537c99fd7d2e74e4943662e224"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["Controls how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 65.1.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "20": {"facts": [{"label": "Applies to", "value": "GiST indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=20", "label": "CREATE INDEX"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 20 English manual", "sha256": "33a4425c008678a8009be08f283f4f536180f45ebf9f6c2183f06daa3cf385d8"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["Controls how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 65.1.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}}, "content_hash": "18874331d5bd5b014f376a2ed612d9534abad0f75b11f924f580507c8f6f3db7", "imported_at": "2026-09-27T09:57:58.917", "url": "/wiki/relopts/gist-fillfactor/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/gist-fillfactor/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/gist-fillfactor/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/gist-fillfactor/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/gist-fillfactor/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/gist-fillfactor/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/gist-fillfactor/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/gist-fillfactor/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/gist-fillfactor/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/gist-fillfactor/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/gist-fillfactor/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/gist-fillfactor/?v=20"}], "present": true}, {"slug": "hash-fillfactor", "name": "fillfactor", "name_zh": "Hash indexes fillfactor", "category": "Hash indexes", "summary": "Controls how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "aliases": ["hash.fillfactor"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "Hash indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=10", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS", "path": "sql-createindex.html", "label": "PostgreSQL 10 English manual", "sha256": "7b1817d528a7de6c346b120316ca74abde75ccf0f2f21c34a72dbe032a88e403"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to Hash indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index build, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to gradual degradation in the index's efficiency. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected. If the table is static then fillfactor 100 is best to minimize the index's physical size, but for heavily updated tables a smaller fillfactor is better to minimize the need for page splits. The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "11": {"facts": [{"label": "Applies to", "value": "Hash indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=11", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS", "path": "sql-createindex.html", "label": "PostgreSQL 11 English manual", "sha256": "e7cfb07816fa696f1a7d5a3a8c43287796d08f48bddd6b2413279895b57ff2da"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to Hash indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index build, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to gradual degradation in the index's efficiency. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected. If the table is static then fillfactor 100 is best to minimize the index's physical size, but for heavily updated tables a smaller fillfactor is better to minimize the need for page splits. The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "12": {"facts": [{"label": "Applies to", "value": "Hash indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=12", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 12 English manual", "sha256": "deedeb34af9b62564d13ab2d379b31b19d4de6fb89a0e712826211914a0c5805"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to Hash indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index build, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to gradual degradation in the index's efficiency. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected. If the table is static then fillfactor 100 is best to minimize the index's physical size, but for heavily updated tables a smaller fillfactor is better to minimize the need for page splits. The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "13": {"facts": [{"label": "Applies to", "value": "Hash indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=13", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 13 English manual", "sha256": "a02f612ec64fc7396ab65a1ce4458cd6971bbd8715e2465ae3c5927d20af3840"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to Hash indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index build, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to gradual degradation in the index's efficiency. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected. If the table is static then fillfactor 100 is best to minimize the index's physical size, but for heavily updated tables a smaller fillfactor is better to minimize the need for page splits. The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "14": {"facts": [{"label": "Applies to", "value": "Hash indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=14", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 14 English manual", "sha256": "f4d42bd08081490a491dc7bf4fa78b2a49da55ebcd0e7f843862548f7c66d70d"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to Hash indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 64.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "15": {"facts": [{"label": "Applies to", "value": "Hash indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=15", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 15 English manual", "sha256": "d0c693e7bccb80a261cfefed9f515fd2d24fb49395dfcbd61672d7915fa0666c"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to Hash indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 67.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "16": {"facts": [{"label": "Applies to", "value": "Hash indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=16", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 16 English manual", "sha256": "ede5053e24573587783eee1735daf6cba76010c2773f10ad066d8cdaf7073c83"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to Hash indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 67.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "17": {"facts": [{"label": "Applies to", "value": "Hash indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=17", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 17 English manual", "sha256": "7fdb46b4a32c524457958417502f4036888552e0577352ee66f107019bbfffd6"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to Hash indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 64.1.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "18": {"facts": [{"label": "Applies to", "value": "Hash indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=18", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 18 English manual", "sha256": "6aa00da55815d13d0355dd25cb1cdb603fa36964993f164d1b6f486011282580"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to Hash indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["Controls how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 65.1.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "19": {"facts": [{"label": "Applies to", "value": "Hash indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=19", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 19 English manual", "sha256": "e90c2051c335f6636fb68f3b03f98c3282445c537c99fd7d2e74e4943662e224"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to Hash indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["Controls how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 65.1.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "20": {"facts": [{"label": "Applies to", "value": "Hash indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=20", "label": "CREATE INDEX"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 20 English manual", "sha256": "33a4425c008678a8009be08f283f4f536180f45ebf9f6c2183f06daa3cf385d8"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to Hash indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["Controls how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 65.1.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}}, "content_hash": "2a674f9028e6c5ebe068c2c20f2db36c3d7e782e4116275860c5b9d317c4f269", "imported_at": "2026-09-27T09:57:58.919", "url": "/wiki/relopts/hash-fillfactor/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/hash-fillfactor/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/hash-fillfactor/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/hash-fillfactor/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/hash-fillfactor/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/hash-fillfactor/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/hash-fillfactor/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/hash-fillfactor/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/hash-fillfactor/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/hash-fillfactor/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/hash-fillfactor/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/hash-fillfactor/?v=20"}], "present": true}, {"slug": "spgist-fillfactor", "name": "fillfactor", "name_zh": "SP-GiST indexes fillfactor", "category": "SP-GiST indexes", "summary": "Controls how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "aliases": ["spgist.fillfactor"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "SP-GiST indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=10", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS", "path": "sql-createindex.html", "label": "PostgreSQL 10 English manual", "sha256": "7b1817d528a7de6c346b120316ca74abde75ccf0f2f21c34a72dbe032a88e403"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to SP-GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index build, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to gradual degradation in the index's efficiency. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected. If the table is static then fillfactor 100 is best to minimize the index's physical size, but for heavily updated tables a smaller fillfactor is better to minimize the need for page splits. The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "11": {"facts": [{"label": "Applies to", "value": "SP-GiST indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=11", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS", "path": "sql-createindex.html", "label": "PostgreSQL 11 English manual", "sha256": "e7cfb07816fa696f1a7d5a3a8c43287796d08f48bddd6b2413279895b57ff2da"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to SP-GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index build, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to gradual degradation in the index's efficiency. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected. If the table is static then fillfactor 100 is best to minimize the index's physical size, but for heavily updated tables a smaller fillfactor is better to minimize the need for page splits. The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "12": {"facts": [{"label": "Applies to", "value": "SP-GiST indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=12", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 12 English manual", "sha256": "deedeb34af9b62564d13ab2d379b31b19d4de6fb89a0e712826211914a0c5805"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to SP-GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index build, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to gradual degradation in the index's efficiency. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected. If the table is static then fillfactor 100 is best to minimize the index's physical size, but for heavily updated tables a smaller fillfactor is better to minimize the need for page splits. The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "13": {"facts": [{"label": "Applies to", "value": "SP-GiST indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=13", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 13 English manual", "sha256": "a02f612ec64fc7396ab65a1ce4458cd6971bbd8715e2465ae3c5927d20af3840"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to SP-GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index build, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to gradual degradation in the index's efficiency. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected. If the table is static then fillfactor 100 is best to minimize the index's physical size, but for heavily updated tables a smaller fillfactor is better to minimize the need for page splits. The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "14": {"facts": [{"label": "Applies to", "value": "SP-GiST indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=14", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 14 English manual", "sha256": "f4d42bd08081490a491dc7bf4fa78b2a49da55ebcd0e7f843862548f7c66d70d"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to SP-GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 64.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "15": {"facts": [{"label": "Applies to", "value": "SP-GiST indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=15", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 15 English manual", "sha256": "d0c693e7bccb80a261cfefed9f515fd2d24fb49395dfcbd61672d7915fa0666c"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to SP-GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 67.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "16": {"facts": [{"label": "Applies to", "value": "SP-GiST indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=16", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 16 English manual", "sha256": "ede5053e24573587783eee1735daf6cba76010c2773f10ad066d8cdaf7073c83"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to SP-GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 67.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "17": {"facts": [{"label": "Applies to", "value": "SP-GiST indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=17", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 17 English manual", "sha256": "7fdb46b4a32c524457958417502f4036888552e0577352ee66f107019bbfffd6"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to SP-GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for an index is a percentage that determines how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 64.1.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "18": {"facts": [{"label": "Applies to", "value": "SP-GiST indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=18", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 18 English manual", "sha256": "6aa00da55815d13d0355dd25cb1cdb603fa36964993f164d1b6f486011282580"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to SP-GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["Controls how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 65.1.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "19": {"facts": [{"label": "Applies to", "value": "SP-GiST indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=19", "label": "CREATE INDEX"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 19 English manual", "sha256": "e90c2051c335f6636fb68f3b03f98c3282445c537c99fd7d2e74e4943662e224"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to SP-GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["Controls how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 65.1.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}, "20": {"facts": [{"label": "Applies to", "value": "SP-GiST indexes"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-index/?v=20", "label": "CREATE INDEX"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createindex.html#INDEX-RELOPTION-FILLFACTOR", "path": "sql-createindex.html", "label": "PostgreSQL 20 English manual", "sha256": "33a4425c008678a8009be08f283f4f536180f45ebf9f6c2183f06daa3cf385d8"}], "sections": [{"title": "Index access method", "paragraphs": ["This entry applies to SP-GiST indexes. Set it with CREATE INDEX WITH or ALTER INDEX SET. Read defaults and behavior for this specific access method.", "The manual groups four access methods under fillfactor. Its default of 90 and range of 10\u2013100 refer specifically to B-tree."]}], "signature": "WITH (fillfactor = value)", "description": ["Controls how full the index method will try to pack index pages. For B-trees, leaf pages are filled to this percentage during initial index builds, and also when extending the index at the right (adding new largest key values). If pages subsequently become completely full, they will be split, leading to fragmentation of the on-disk index structure. B-trees use a default fillfactor of 90, but any integer value from 10 to 100 can be selected.", "B-tree indexes on tables where many inserts and/or updates are anticipated can benefit from lower fillfactor settings at CREATE INDEX time (following bulk loading into the table). Values in the range of 50 - 90 can usefully \u201c smooth out \u201d the rate of page splits during the early life of the B-tree index (lowering fillfactor like this may even lower the absolute number of page splits, though this effect is highly workload dependent). The B-tree bottom-up index deletion technique described in Section 65.1.4.2 is dependent on having some \u201c extra \u201d space on pages to store \u201c extra \u201d tuple versions, and so can be affected by fillfactor (though the effect is usually not significant).", "In other specific cases it might be useful to increase fillfactor to 100 at CREATE INDEX time as a way of maximizing space utilization. You should only consider this when you are completely sure that the table is static (i.e. that it will never be affected by either inserts or updates). A fillfactor setting of 100 otherwise risks harming performance: even a few updates or inserts will cause a sudden flood of page splits.", "The other index methods use fillfactor in different but roughly analogous ways; the default fillfactor varies between methods."]}}, "content_hash": "cb238eff4a7157bca8325a55aa8802ecccb05e144110686a328f5cb7326cb4df", "imported_at": "2026-09-27T09:57:58.921", "url": "/wiki/relopts/spgist-fillfactor/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/spgist-fillfactor/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/spgist-fillfactor/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/spgist-fillfactor/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/spgist-fillfactor/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/spgist-fillfactor/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/spgist-fillfactor/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/spgist-fillfactor/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/spgist-fillfactor/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/spgist-fillfactor/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/spgist-fillfactor/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/spgist-fillfactor/?v=20"}], "present": true}, {"slug": "toast-autovacuum-enabled", "name": "toast.autovacuum_enabled", "name_zh": "TOAST autovacuum_enabled", "category": "TOAST tables", "summary": "Enables or disables the autovacuum daemon for a particular table. If true, the autovacuum daemon will perform automatic VACUUM and/or ANALYZE operations on this table following the rules discussed in Section 24.1.6 . If false, this table will not be autovacuumed, except to prevent transaction ID wraparound. See Section 24.1.5 for more about wraparound prevention. Note that the autovacuum daemon does not run at all (except to prevent transaction ID wraparound) if the autovacuum parameter is false; setting individual tables' storage parameters does not override that. Therefore there is seldom much point in explicitly setting this storage parameter to true , only to false .", "aliases": ["autovacuum_enabled"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/relopts/table-autovacuum-enabled/?v=10", "label": "Table option autovacuum_enabled"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}], "signature": "WITH (toast.autovacuum_enabled = value)", "description": ["Enables or disables the autovacuum daemon for a particular table. If true, the autovacuum daemon will perform automatic VACUUM and/or ANALYZE operations on this table following the rules discussed in Section 24.1.6 . If false, this table will not be autovacuumed, except to prevent transaction ID wraparound. See Section 24.1.5 for more about wraparound prevention. Note that the autovacuum daemon does not run at all (except to prevent transaction ID wraparound) if the autovacuum parameter is false; setting individual tables' storage parameters does not override that. Therefore there is seldom much point in explicitly setting this storage parameter to true , only to false ."]}, "11": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/relopts/table-autovacuum-enabled/?v=11", "label": "Table option autovacuum_enabled"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}], "signature": "WITH (toast.autovacuum_enabled = value)", "description": ["Enables or disables the autovacuum daemon for a particular table. If true, the autovacuum daemon will perform automatic VACUUM and/or ANALYZE operations on this table following the rules discussed in Section 24.1.6 . If false, this table will not be autovacuumed, except to prevent transaction ID wraparound. See Section 24.1.5 for more about wraparound prevention. Note that the autovacuum daemon does not run at all (except to prevent transaction ID wraparound) if the autovacuum parameter is false; setting individual tables' storage parameters does not override that. Therefore there is seldom much point in explicitly setting this storage parameter to true , only to false ."]}, "12": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/relopts/table-autovacuum-enabled/?v=12", "label": "Table option autovacuum_enabled"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-AUTOVACUUM-ENABLED", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast.autovacuum_enabled = value)", "description": ["Enables or disables the autovacuum daemon for a particular table. If true, the autovacuum daemon will perform automatic VACUUM and/or ANALYZE operations on this table following the rules discussed in Section 24.1.6 . If false, this table will not be autovacuumed, except to prevent transaction ID wraparound. See Section 24.1.5 for more about wraparound prevention. Note that the autovacuum daemon does not run at all (except to prevent transaction ID wraparound) if the autovacuum parameter is false; setting individual tables' storage parameters does not override that. Therefore there is seldom much point in explicitly setting this storage parameter to true , only to false ."]}, "13": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/relopts/table-autovacuum-enabled/?v=13", "label": "Table option autovacuum_enabled"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-ENABLED", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast.autovacuum_enabled = value)", "description": ["Enables or disables the autovacuum daemon for a particular table. If true, the autovacuum daemon will perform automatic VACUUM and/or ANALYZE operations on this table following the rules discussed in Section 24.1.6 . If false, this table will not be autovacuumed, except to prevent transaction ID wraparound. See Section 24.1.5 for more about wraparound prevention. Note that the autovacuum daemon does not run at all (except to prevent transaction ID wraparound) if the autovacuum parameter is false; setting individual tables' storage parameters does not override that. Therefore there is seldom much point in explicitly setting this storage parameter to true , only to false ."]}, "14": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/relopts/table-autovacuum-enabled/?v=14", "label": "Table option autovacuum_enabled"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-ENABLED", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast.autovacuum_enabled = value)", "description": ["Enables or disables the autovacuum daemon for a particular table. If true, the autovacuum daemon will perform automatic VACUUM and/or ANALYZE operations on this table following the rules discussed in Section 25.1.6 . If false, this table will not be autovacuumed, except to prevent transaction ID wraparound. See Section 25.1.5 for more about wraparound prevention. Note that the autovacuum daemon does not run at all (except to prevent transaction ID wraparound) if the autovacuum parameter is false; setting individual tables' storage parameters does not override that. Therefore there is seldom much point in explicitly setting this storage parameter to true , only to false ."]}, "15": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/relopts/table-autovacuum-enabled/?v=15", "label": "Table option autovacuum_enabled"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-ENABLED", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast.autovacuum_enabled = value)", "description": ["Enables or disables the autovacuum daemon for a particular table. If true, the autovacuum daemon will perform automatic VACUUM and/or ANALYZE operations on this table following the rules discussed in Section 25.1.6 . If false, this table will not be autovacuumed, except to prevent transaction ID wraparound. See Section 25.1.5 for more about wraparound prevention. Note that the autovacuum daemon does not run at all (except to prevent transaction ID wraparound) if the autovacuum parameter is false; setting individual tables' storage parameters does not override that. Therefore there is seldom much point in explicitly setting this storage parameter to true , only to false ."]}, "16": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/relopts/table-autovacuum-enabled/?v=16", "label": "Table option autovacuum_enabled"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-ENABLED", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast.autovacuum_enabled = value)", "description": ["Enables or disables the autovacuum daemon for a particular table. If true, the autovacuum daemon will perform automatic VACUUM and/or ANALYZE operations on this table following the rules discussed in Section 25.1.6 . If false, this table will not be autovacuumed, except to prevent transaction ID wraparound. See Section 25.1.5 for more about wraparound prevention. Note that the autovacuum daemon does not run at all (except to prevent transaction ID wraparound) if the autovacuum parameter is false; setting individual tables' storage parameters does not override that. Therefore there is seldom much point in explicitly setting this storage parameter to true , only to false ."]}, "17": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/relopts/table-autovacuum-enabled/?v=17", "label": "Table option autovacuum_enabled"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-ENABLED", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast.autovacuum_enabled = value)", "description": ["Enables or disables the autovacuum daemon for a particular table. If true, the autovacuum daemon will perform automatic VACUUM and/or ANALYZE operations on this table following the rules discussed in Section 24.1.6 . If false, this table will not be autovacuumed, except to prevent transaction ID wraparound. See Section 24.1.5 for more about wraparound prevention. Note that the autovacuum daemon does not run at all (except to prevent transaction ID wraparound) if the autovacuum parameter is false; setting individual tables' storage parameters does not override that. Therefore there is seldom much point in explicitly setting this storage parameter to true , only to false ."]}, "18": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/relopts/table-autovacuum-enabled/?v=18", "label": "Table option autovacuum_enabled"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-ENABLED", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast.autovacuum_enabled = value)", "description": ["Enables or disables the autovacuum daemon for a particular table. If true, the autovacuum daemon will perform automatic VACUUM and/or ANALYZE operations on this table following the rules discussed in Section 24.1.6 . If false, this table will not be autovacuumed, except to prevent transaction ID wraparound. See Section 24.1.5 for more about wraparound prevention. Note that the autovacuum daemon does not run at all (except to prevent transaction ID wraparound) if the autovacuum parameter is false; setting individual tables' storage parameters does not override that. Therefore there is seldom much point in explicitly setting this storage parameter to true , only to false ."]}, "19": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/relopts/table-autovacuum-enabled/?v=19", "label": "Table option autovacuum_enabled"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-ENABLED", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast.autovacuum_enabled = value)", "description": ["Enables or disables the autovacuum daemon for a particular table. If true, the autovacuum daemon will perform automatic VACUUM and/or ANALYZE operations on this table following the rules discussed in Section 24.1.6 . If false, this table will not be autovacuumed, except to prevent transaction ID wraparound. See Section 24.1.5 for more about wraparound prevention. Note that the autovacuum daemon does not run at all (except to prevent transaction ID wraparound) if the autovacuum parameter is false; setting individual tables' storage parameters does not override that. Therefore there is seldom much point in explicitly setting this storage parameter to true , only to false ."]}, "20": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/relopts/table-autovacuum-enabled/?v=20", "label": "Table option autovacuum_enabled"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-ENABLED", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast.autovacuum_enabled = value)", "description": ["Enables or disables the autovacuum daemon for a particular table. If true, the autovacuum daemon will perform automatic VACUUM and/or ANALYZE operations on this table following the rules discussed in Section 24.1.6 . If false, this table will not be autovacuumed, except to prevent transaction ID wraparound. See Section 24.1.5 for more about wraparound prevention. Note that the autovacuum daemon does not run at all (except to prevent transaction ID wraparound) if the autovacuum parameter is false; setting individual tables' storage parameters does not override that. Therefore there is seldom much point in explicitly setting this storage parameter to true , only to false ."]}}, "content_hash": "182d3da594babdfb1d06b4506c8666a4e28167dc47823f021eb115f9343d6f8b", "imported_at": "2026-09-27T09:57:58.980", "url": "/wiki/relopts/toast-autovacuum-enabled/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-enabled/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-enabled/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-enabled/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-enabled/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-enabled/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-enabled/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-enabled/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-enabled/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-enabled/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-enabled/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-enabled/?v=20"}], "present": true}, {"slug": "toast-autovacuum-freeze-max-age", "name": "toast.autovacuum_freeze_max_age", "name_zh": "TOAST autovacuum_freeze_max_age", "category": "TOAST tables", "summary": "Per-table value for autovacuum_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller).", "aliases": ["autovacuum_freeze_max_age"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-max-age/?v=10", "label": "Table option autovacuum_freeze_max_age"}, {"url": "/docs/guc/autovacuum_freeze_max_age/?v=10", "label": "Global parameter autovacuum_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_freeze_max_age", "sha256": "a8c8d51fd43c0e169a2ce6bcb094c1dbd5f0f6cd6e90cabc86f6542039600355"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in transactions) that a table's pg_class . relfrozenxid field can attain before a VACUUM operation is forced to prevent transaction ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuum also allows removal of old files from the pg_xact subdirectory, which is why the default is a relatively low 200 million transactions. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_max_age = value)", "description": ["Per-table value for autovacuum_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "11": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-max-age/?v=11", "label": "Table option autovacuum_freeze_max_age"}, {"url": "/docs/guc/autovacuum_freeze_max_age/?v=11", "label": "Global parameter autovacuum_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_freeze_max_age", "sha256": "a553adbaa0edb4dbdf216a59031edf5974a2791c02e12f3a6f23a0df0cdc59d1"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in transactions) that a table's pg_class . relfrozenxid field can attain before a VACUUM operation is forced to prevent transaction ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuum also allows removal of old files from the pg_xact subdirectory, which is why the default is a relatively low 200 million transactions. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_max_age = value)", "description": ["Per-table value for autovacuum_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "12": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-max-age/?v=12", "label": "Table option autovacuum_freeze_max_age"}, {"url": "/docs/guc/autovacuum_freeze_max_age/?v=12", "label": "Global parameter autovacuum_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_freeze_max_age", "sha256": "bb486d78e8d17e633e046674781b62e0cf0f77efbb48cd6fffa5fd6b34ac98e6"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in transactions) that a table's pg_class . relfrozenxid field can attain before a VACUUM operation is forced to prevent transaction ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuum also allows removal of old files from the pg_xact subdirectory, which is why the default is a relatively low 200 million transactions. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_max_age = value)", "description": ["Per-table value for autovacuum_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "13": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-max-age/?v=13", "label": "Table option autovacuum_freeze_max_age"}, {"url": "/docs/guc/autovacuum_freeze_max_age/?v=13", "label": "Global parameter autovacuum_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_freeze_max_age", "sha256": "d26d014ad3850d3dbbbc1bce41bc267205baa1523b73e48fdd9e7165b6f6785e"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in transactions) that a table's pg_class . relfrozenxid field can attain before a VACUUM operation is forced to prevent transaction ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuum also allows removal of old files from the pg_xact subdirectory, which is why the default is a relatively low 200 million transactions. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_max_age = value)", "description": ["Per-table value for autovacuum_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "14": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-max-age/?v=14", "label": "Table option autovacuum_freeze_max_age"}, {"url": "/docs/guc/autovacuum_freeze_max_age/?v=14", "label": "Global parameter autovacuum_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_freeze_max_age", "sha256": "03e821969b789b688f725579aa8bd52763880e798ca8680d894f2c12861724cf"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in transactions) that a table's pg_class . relfrozenxid field can attain before a VACUUM operation is forced to prevent transaction ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuum also allows removal of old files from the pg_xact subdirectory, which is why the default is a relatively low 200 million transactions. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 25.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_max_age = value)", "description": ["Per-table value for autovacuum_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "15": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-max-age/?v=15", "label": "Table option autovacuum_freeze_max_age"}, {"url": "/docs/guc/autovacuum_freeze_max_age/?v=15", "label": "Global parameter autovacuum_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_freeze_max_age", "sha256": "993bb5fe87856e4c4cb9aedac41232b5915272a65226f57e7fbf0713be2b13f4"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in transactions) that a table's pg_class . relfrozenxid field can attain before a VACUUM operation is forced to prevent transaction ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuum also allows removal of old files from the pg_xact subdirectory, which is why the default is a relatively low 200 million transactions. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 25.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_max_age = value)", "description": ["Per-table value for autovacuum_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "16": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-max-age/?v=16", "label": "Table option autovacuum_freeze_max_age"}, {"url": "/docs/guc/autovacuum_freeze_max_age/?v=16", "label": "Global parameter autovacuum_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_freeze_max_age", "sha256": "b16c76b3ffb04e1e6601c44b44e2237f2a97916a52ca9b156a820abdf6545547"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in transactions) that a table's pg_class . relfrozenxid field can attain before a VACUUM operation is forced to prevent transaction ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuum also allows removal of old files from the pg_xact subdirectory, which is why the default is a relatively low 200 million transactions. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 25.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_max_age = value)", "description": ["Per-table value for autovacuum_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "17": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-max-age/?v=17", "label": "Table option autovacuum_freeze_max_age"}, {"url": "/docs/guc/autovacuum_freeze_max_age/?v=17", "label": "Global parameter autovacuum_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_freeze_max_age", "sha256": "8caf714d72c9f2ed5f0f8d65041109e0ab8845c7c1169c0febef5193bdaef36d"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in transactions) that a table's pg_class . relfrozenxid field can attain before a VACUUM operation is forced to prevent transaction ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuum also allows removal of old files from the pg_xact subdirectory, which is why the default is a relatively low 200 million transactions. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_max_age = value)", "description": ["Per-table value for autovacuum_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "18": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-max-age/?v=18", "label": "Table option autovacuum_freeze_max_age"}, {"url": "/docs/guc/autovacuum_freeze_max_age/?v=18", "label": "Global parameter autovacuum_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_freeze_max_age", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in transactions) that a table's pg_class . relfrozenxid field can attain before a VACUUM operation is forced to prevent transaction ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuum also allows removal of old files from the pg_xact subdirectory, which is why the default is a relatively low 200 million transactions. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_max_age = value)", "description": ["Per-table value for autovacuum_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "19": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-max-age/?v=19", "label": "Table option autovacuum_freeze_max_age"}, {"url": "/docs/guc/autovacuum_freeze_max_age/?v=19", "label": "Global parameter autovacuum_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_freeze_max_age", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in transactions) that a table's pg_class . relfrozenxid field can attain before a VACUUM operation is forced to prevent transaction ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuum also allows removal of old files from the pg_xact subdirectory, which is why the default is a relatively low 200 million transactions. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_max_age = value)", "description": ["Per-table value for autovacuum_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "20": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-max-age/?v=20", "label": "Table option autovacuum_freeze_max_age"}, {"url": "/docs/guc/autovacuum_freeze_max_age/?v=20", "label": "Global parameter autovacuum_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_freeze_max_age", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in transactions) that a table's pg_class . relfrozenxid field can attain before a VACUUM operation is forced to prevent transaction ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuum also allows removal of old files from the pg_xact subdirectory, which is why the default is a relatively low 200 million transactions. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_max_age = value)", "description": ["Per-table value for autovacuum_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}}, "content_hash": "c59084bb7e2103b8eb054b94b4c4110b8f12b414f272da5ba6cb96a460e8627e", "imported_at": "2026-09-27T09:57:58.983", "url": "/wiki/relopts/toast-autovacuum-freeze-max-age/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-max-age/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-max-age/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-max-age/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-max-age/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-max-age/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-max-age/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-max-age/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-max-age/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-max-age/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-max-age/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-max-age/?v=20"}], "present": true}, {"slug": "toast-autovacuum-freeze-min-age", "name": "toast.autovacuum_freeze_min_age", "name_zh": "TOAST autovacuum_freeze_min_age", "category": "TOAST tables", "summary": "Per-table value for vacuum_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_min_age parameters that are larger than half the system-wide autovacuum_freeze_max_age setting.", "aliases": ["autovacuum_freeze_min_age"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-min-age/?v=10", "label": "Table option autovacuum_freeze_min_age"}, {"url": "/docs/guc/vacuum_freeze_min_age/?v=10", "label": "Global parameter vacuum_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/runtime-config-client.html#GUC-VACUUM-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_min_age", "sha256": "81c199a46b03a65a060e25cf874fc7ddd28b18261a6472a912954073556935b4"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in transactions) that VACUUM should use to decide whether to freeze row versions while scanning a table. The default is 50 million transactions. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_min_age = value)", "description": ["Per-table value for vacuum_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_min_age parameters that are larger than half the system-wide autovacuum_freeze_max_age setting."]}, "11": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-min-age/?v=11", "label": "Table option autovacuum_freeze_min_age"}, {"url": "/docs/guc/vacuum_freeze_min_age/?v=11", "label": "Global parameter vacuum_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/runtime-config-client.html#GUC-VACUUM-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_min_age", "sha256": "488947b3f6c09ac9a815b8602e852239936b403ef214249fee7aeca1469c25ba"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in transactions) that VACUUM should use to decide whether to freeze row versions while scanning a table. The default is 50 million transactions. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_min_age = value)", "description": ["Per-table value for vacuum_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_min_age parameters that are larger than half the system-wide autovacuum_freeze_max_age setting."]}, "12": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-min-age/?v=12", "label": "Table option autovacuum_freeze_min_age"}, {"url": "/docs/guc/vacuum_freeze_min_age/?v=12", "label": "Global parameter vacuum_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/runtime-config-client.html#GUC-VACUUM-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_min_age", "sha256": "7f27882cdde3b36cef070cdd14ce3f080b65ed837d3f6b41f3faf454ba89cc63"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in transactions) that VACUUM should use to decide whether to freeze row versions while scanning a table. The default is 50 million transactions. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_min_age = value)", "description": ["Per-table value for vacuum_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_min_age parameters that are larger than half the system-wide autovacuum_freeze_max_age setting."]}, "13": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-min-age/?v=13", "label": "Table option autovacuum_freeze_min_age"}, {"url": "/docs/guc/vacuum_freeze_min_age/?v=13", "label": "Global parameter vacuum_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-client.html#GUC-VACUUM-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_min_age", "sha256": "5d70022f2524a39e7c5745698de51d867f687c70394779ad154e05648e923c7d"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in transactions) that VACUUM should use to decide whether to freeze row versions while scanning a table. The default is 50 million transactions. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_min_age = value)", "description": ["Per-table value for vacuum_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_min_age parameters that are larger than half the system-wide autovacuum_freeze_max_age setting."]}, "14": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-min-age/?v=14", "label": "Table option autovacuum_freeze_min_age"}, {"url": "/docs/guc/vacuum_freeze_min_age/?v=14", "label": "Global parameter vacuum_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-client.html#GUC-VACUUM-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_min_age", "sha256": "35d48bb20f151039202a7cafbe7c4ffb109262110d62b2ab75844a3d80c2cebb"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in transactions) that VACUUM should use to decide whether to freeze row versions while scanning a table. The default is 50 million transactions. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 25.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_min_age = value)", "description": ["Per-table value for vacuum_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_min_age parameters that are larger than half the system-wide autovacuum_freeze_max_age setting."]}, "15": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-min-age/?v=15", "label": "Table option autovacuum_freeze_min_age"}, {"url": "/docs/guc/vacuum_freeze_min_age/?v=15", "label": "Global parameter vacuum_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-client.html#GUC-VACUUM-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_min_age", "sha256": "fdcf588ddeeac62758840aa3b8d6ead7e37e1b0c72795e339f67db5b23509462"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in transactions) that VACUUM should use to decide whether to freeze row versions while scanning a table. The default is 50 million transactions. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 25.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_min_age = value)", "description": ["Per-table value for vacuum_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_min_age parameters that are larger than half the system-wide autovacuum_freeze_max_age setting."]}, "16": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-min-age/?v=16", "label": "Table option autovacuum_freeze_min_age"}, {"url": "/docs/guc/vacuum_freeze_min_age/?v=16", "label": "Global parameter vacuum_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-client.html#GUC-VACUUM-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_min_age", "sha256": "e7e096464bd87b0bfc06652cdbbdd175f7a0e955207580049eae2ee394566b20"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in transactions) that VACUUM should use to decide whether to trigger freezing of pages that have an older XID. The default is 50 million transactions. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 25.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_min_age = value)", "description": ["Per-table value for vacuum_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_min_age parameters that are larger than half the system-wide autovacuum_freeze_max_age setting."]}, "17": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-min-age/?v=17", "label": "Table option autovacuum_freeze_min_age"}, {"url": "/docs/guc/vacuum_freeze_min_age/?v=17", "label": "Global parameter vacuum_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-client.html#GUC-VACUUM-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_min_age", "sha256": "e7ba41a33997d251c23f06ccf17978bf1481db92a2c607026f59af86c25d6f50"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in transactions) that VACUUM should use to decide whether to trigger freezing of pages that have an older XID. The default is 50 million transactions. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_min_age = value)", "description": ["Per-table value for vacuum_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_min_age parameters that are larger than half the system-wide autovacuum_freeze_max_age setting."]}, "18": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-min-age/?v=18", "label": "Table option autovacuum_freeze_min_age"}, {"url": "/docs/guc/vacuum_freeze_min_age/?v=18", "label": "Global parameter vacuum_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-VACUUM-FREEZE-MIN-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_freeze_min_age", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in transactions) that VACUUM should use to decide whether to trigger freezing of pages that have an older XID. The default is 50 million transactions. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_min_age = value)", "description": ["Per-table value for vacuum_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_min_age parameters that are larger than half the system-wide autovacuum_freeze_max_age setting."]}, "19": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-min-age/?v=19", "label": "Table option autovacuum_freeze_min_age"}, {"url": "/docs/guc/vacuum_freeze_min_age/?v=19", "label": "Global parameter vacuum_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-VACUUM-FREEZE-MIN-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_freeze_min_age", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in transactions) that VACUUM should use to decide whether to trigger freezing of pages that have an older XID. The default is 50 million transactions. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_min_age = value)", "description": ["Per-table value for vacuum_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_min_age parameters that are larger than half the system-wide autovacuum_freeze_max_age setting."]}, "20": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-min-age/?v=20", "label": "Table option autovacuum_freeze_min_age"}, {"url": "/docs/guc/vacuum_freeze_min_age/?v=20", "label": "Global parameter vacuum_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-VACUUM-FREEZE-MIN-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_freeze_min_age", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in transactions) that VACUUM should use to decide whether to trigger freezing of pages that have an older XID. The default is 50 million transactions. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_min_age = value)", "description": ["Per-table value for vacuum_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_min_age parameters that are larger than half the system-wide autovacuum_freeze_max_age setting."]}}, "content_hash": "fe37ea9b1348917ff80be8342710aa342ef7203eb1220567830968da565c706a", "imported_at": "2026-09-27T09:57:58.986", "url": "/wiki/relopts/toast-autovacuum-freeze-min-age/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-min-age/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-min-age/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-min-age/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-min-age/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-min-age/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-min-age/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-min-age/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-min-age/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-min-age/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-min-age/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-min-age/?v=20"}], "present": true}, {"slug": "toast-autovacuum-freeze-table-age", "name": "toast.autovacuum_freeze_table_age", "name_zh": "TOAST autovacuum_freeze_table_age", "category": "TOAST tables", "summary": "Per-table value for vacuum_freeze_table_age parameter.", "aliases": ["autovacuum_freeze_table_age"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-table-age/?v=10", "label": "Table option autovacuum_freeze_table_age"}, {"url": "/docs/guc/vacuum_freeze_table_age/?v=10", "label": "Global parameter vacuum_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/runtime-config-client.html#GUC-VACUUM-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_table_age", "sha256": "81c199a46b03a65a060e25cf874fc7ddd28b18261a6472a912954073556935b4"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relfrozenxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million transactions. Although users can set this value anywhere from zero to two billions, VACUUM will silently limit the effective value to 95% of autovacuum_freeze_max_age , so that a periodical manual VACUUM has a chance to run before an anti-wraparound autovacuum is launched for the table. For more information see Section 24.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_table_age = value)", "description": ["Per-table value for vacuum_freeze_table_age parameter."]}, "11": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-table-age/?v=11", "label": "Table option autovacuum_freeze_table_age"}, {"url": "/docs/guc/vacuum_freeze_table_age/?v=11", "label": "Global parameter vacuum_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/runtime-config-client.html#GUC-VACUUM-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_table_age", "sha256": "488947b3f6c09ac9a815b8602e852239936b403ef214249fee7aeca1469c25ba"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relfrozenxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million transactions. Although users can set this value anywhere from zero to two billions, VACUUM will silently limit the effective value to 95% of autovacuum_freeze_max_age , so that a periodical manual VACUUM has a chance to run before an anti-wraparound autovacuum is launched for the table. For more information see Section 24.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_table_age = value)", "description": ["Per-table value for vacuum_freeze_table_age parameter."]}, "12": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-table-age/?v=12", "label": "Table option autovacuum_freeze_table_age"}, {"url": "/docs/guc/vacuum_freeze_table_age/?v=12", "label": "Global parameter vacuum_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/runtime-config-client.html#GUC-VACUUM-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_table_age", "sha256": "7f27882cdde3b36cef070cdd14ce3f080b65ed837d3f6b41f3faf454ba89cc63"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relfrozenxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million transactions. Although users can set this value anywhere from zero to two billions, VACUUM will silently limit the effective value to 95% of autovacuum_freeze_max_age , so that a periodical manual VACUUM has a chance to run before an anti-wraparound autovacuum is launched for the table. For more information see Section 24.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_table_age = value)", "description": ["Per-table value for vacuum_freeze_table_age parameter."]}, "13": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-table-age/?v=13", "label": "Table option autovacuum_freeze_table_age"}, {"url": "/docs/guc/vacuum_freeze_table_age/?v=13", "label": "Global parameter vacuum_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-client.html#GUC-VACUUM-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_table_age", "sha256": "5d70022f2524a39e7c5745698de51d867f687c70394779ad154e05648e923c7d"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relfrozenxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million transactions. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound autovacuum is launched for the table. For more information see Section 24.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_table_age = value)", "description": ["Per-table value for vacuum_freeze_table_age parameter."]}, "14": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-table-age/?v=14", "label": "Table option autovacuum_freeze_table_age"}, {"url": "/docs/guc/vacuum_freeze_table_age/?v=14", "label": "Global parameter vacuum_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-client.html#GUC-VACUUM-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_table_age", "sha256": "35d48bb20f151039202a7cafbe7c4ffb109262110d62b2ab75844a3d80c2cebb"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relfrozenxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million transactions. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound autovacuum is launched for the table. For more information see Section 25.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_table_age = value)", "description": ["Per-table value for vacuum_freeze_table_age parameter."]}, "15": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-table-age/?v=15", "label": "Table option autovacuum_freeze_table_age"}, {"url": "/docs/guc/vacuum_freeze_table_age/?v=15", "label": "Global parameter vacuum_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-client.html#GUC-VACUUM-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_table_age", "sha256": "fdcf588ddeeac62758840aa3b8d6ead7e37e1b0c72795e339f67db5b23509462"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relfrozenxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million transactions. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound autovacuum is launched for the table. For more information see Section 25.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_table_age = value)", "description": ["Per-table value for vacuum_freeze_table_age parameter."]}, "16": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-table-age/?v=16", "label": "Table option autovacuum_freeze_table_age"}, {"url": "/docs/guc/vacuum_freeze_table_age/?v=16", "label": "Global parameter vacuum_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-client.html#GUC-VACUUM-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_table_age", "sha256": "e7e096464bd87b0bfc06652cdbbdd175f7a0e955207580049eae2ee394566b20"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relfrozenxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million transactions. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound autovacuum is launched for the table. For more information see Section 25.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_table_age = value)", "description": ["Per-table value for vacuum_freeze_table_age parameter."]}, "17": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-table-age/?v=17", "label": "Table option autovacuum_freeze_table_age"}, {"url": "/docs/guc/vacuum_freeze_table_age/?v=17", "label": "Global parameter vacuum_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-client.html#GUC-VACUUM-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_table_age", "sha256": "e7ba41a33997d251c23f06ccf17978bf1481db92a2c607026f59af86c25d6f50"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relfrozenxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million transactions. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound autovacuum is launched for the table. For more information see Section 24.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_table_age = value)", "description": ["Per-table value for vacuum_freeze_table_age parameter."]}, "18": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-table-age/?v=18", "label": "Table option autovacuum_freeze_table_age"}, {"url": "/docs/guc/vacuum_freeze_table_age/?v=18", "label": "Global parameter vacuum_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-VACUUM-FREEZE-TABLE-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_freeze_table_age", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relfrozenxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million transactions. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound autovacuum is launched for the table. For more information see Section 24.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_table_age = value)", "description": ["Per-table value for vacuum_freeze_table_age parameter."]}, "19": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-table-age/?v=19", "label": "Table option autovacuum_freeze_table_age"}, {"url": "/docs/guc/vacuum_freeze_table_age/?v=19", "label": "Global parameter vacuum_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-VACUUM-FREEZE-TABLE-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_freeze_table_age", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relfrozenxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million transactions. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound autovacuum is launched for the table. For more information see Section 24.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_table_age = value)", "description": ["Per-table value for vacuum_freeze_table_age parameter."]}, "20": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-freeze-table-age/?v=20", "label": "Table option autovacuum_freeze_table_age"}, {"url": "/docs/guc/vacuum_freeze_table_age/?v=20", "label": "Global parameter vacuum_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-VACUUM-FREEZE-TABLE-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_freeze_table_age", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relfrozenxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million transactions. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound autovacuum is launched for the table. For more information see Section 24.1.5 ."]}], "signature": "WITH (toast.autovacuum_freeze_table_age = value)", "description": ["Per-table value for vacuum_freeze_table_age parameter."]}}, "content_hash": "eaf1fe391ad73c70091cf0703400daf7c1554fdc7c633796cad554f12d81ad69", "imported_at": "2026-09-27T09:57:58.988", "url": "/wiki/relopts/toast-autovacuum-freeze-table-age/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-table-age/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-table-age/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-table-age/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-table-age/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-table-age/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-table-age/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-table-age/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-table-age/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-table-age/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-table-age/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-freeze-table-age/?v=20"}], "present": true}, {"slug": "toast-autovacuum-multixact-freeze-max-age", "name": "toast.autovacuum_multixact_freeze_max_age", "name_zh": "TOAST autovacuum_multixact_freeze_max_age", "category": "TOAST tables", "summary": "Per-table value for autovacuum_multixact_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller).", "aliases": ["autovacuum_multixact_freeze_max_age"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-max-age/?v=10", "label": "Table option autovacuum_multixact_freeze_max_age"}, {"url": "/docs/guc/autovacuum_multixact_freeze_max_age/?v=10", "label": "Global parameter autovacuum_multixact_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/runtime-config-autovacuum.html#GUC-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_multixact_freeze_max_age", "sha256": "a8c8d51fd43c0e169a2ce6bcb094c1dbd5f0f6cd6e90cabc86f6542039600355"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_multixact_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in multixacts) that a table's pg_class . relminmxid field can attain before a VACUUM operation is forced to prevent multixact ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuuming multixacts also allows removal of old files from the pg_multixact/members and pg_multixact/offsets subdirectories, which is why the default is a relatively low 400 million multixacts. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_max_age = value)", "description": ["Per-table value for autovacuum_multixact_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "11": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-max-age/?v=11", "label": "Table option autovacuum_multixact_freeze_max_age"}, {"url": "/docs/guc/autovacuum_multixact_freeze_max_age/?v=11", "label": "Global parameter autovacuum_multixact_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/runtime-config-autovacuum.html#GUC-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_multixact_freeze_max_age", "sha256": "a553adbaa0edb4dbdf216a59031edf5974a2791c02e12f3a6f23a0df0cdc59d1"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_multixact_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in multixacts) that a table's pg_class . relminmxid field can attain before a VACUUM operation is forced to prevent multixact ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuuming multixacts also allows removal of old files from the pg_multixact/members and pg_multixact/offsets subdirectories, which is why the default is a relatively low 400 million multixacts. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_max_age = value)", "description": ["Per-table value for autovacuum_multixact_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "12": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-max-age/?v=12", "label": "Table option autovacuum_multixact_freeze_max_age"}, {"url": "/docs/guc/autovacuum_multixact_freeze_max_age/?v=12", "label": "Global parameter autovacuum_multixact_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/runtime-config-autovacuum.html#GUC-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_multixact_freeze_max_age", "sha256": "bb486d78e8d17e633e046674781b62e0cf0f77efbb48cd6fffa5fd6b34ac98e6"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_multixact_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in multixacts) that a table's pg_class . relminmxid field can attain before a VACUUM operation is forced to prevent multixact ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuuming multixacts also allows removal of old files from the pg_multixact/members and pg_multixact/offsets subdirectories, which is why the default is a relatively low 400 million multixacts. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_max_age = value)", "description": ["Per-table value for autovacuum_multixact_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "13": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-max-age/?v=13", "label": "Table option autovacuum_multixact_freeze_max_age"}, {"url": "/docs/guc/autovacuum_multixact_freeze_max_age/?v=13", "label": "Global parameter autovacuum_multixact_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-autovacuum.html#GUC-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_multixact_freeze_max_age", "sha256": "d26d014ad3850d3dbbbc1bce41bc267205baa1523b73e48fdd9e7165b6f6785e"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_multixact_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in multixacts) that a table's pg_class . relminmxid field can attain before a VACUUM operation is forced to prevent multixact ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuuming multixacts also allows removal of old files from the pg_multixact/members and pg_multixact/offsets subdirectories, which is why the default is a relatively low 400 million multixacts. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_max_age = value)", "description": ["Per-table value for autovacuum_multixact_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "14": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-max-age/?v=14", "label": "Table option autovacuum_multixact_freeze_max_age"}, {"url": "/docs/guc/autovacuum_multixact_freeze_max_age/?v=14", "label": "Global parameter autovacuum_multixact_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-autovacuum.html#GUC-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_multixact_freeze_max_age", "sha256": "03e821969b789b688f725579aa8bd52763880e798ca8680d894f2c12861724cf"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_multixact_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in multixacts) that a table's pg_class . relminmxid field can attain before a VACUUM operation is forced to prevent multixact ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuuming multixacts also allows removal of old files from the pg_multixact/members and pg_multixact/offsets subdirectories, which is why the default is a relatively low 400 million multixacts. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 25.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_max_age = value)", "description": ["Per-table value for autovacuum_multixact_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "15": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-max-age/?v=15", "label": "Table option autovacuum_multixact_freeze_max_age"}, {"url": "/docs/guc/autovacuum_multixact_freeze_max_age/?v=15", "label": "Global parameter autovacuum_multixact_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-autovacuum.html#GUC-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_multixact_freeze_max_age", "sha256": "993bb5fe87856e4c4cb9aedac41232b5915272a65226f57e7fbf0713be2b13f4"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_multixact_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in multixacts) that a table's pg_class . relminmxid field can attain before a VACUUM operation is forced to prevent multixact ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuuming multixacts also allows removal of old files from the pg_multixact/members and pg_multixact/offsets subdirectories, which is why the default is a relatively low 400 million multixacts. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 25.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_max_age = value)", "description": ["Per-table value for autovacuum_multixact_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "16": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-max-age/?v=16", "label": "Table option autovacuum_multixact_freeze_max_age"}, {"url": "/docs/guc/autovacuum_multixact_freeze_max_age/?v=16", "label": "Global parameter autovacuum_multixact_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-autovacuum.html#GUC-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_multixact_freeze_max_age", "sha256": "b16c76b3ffb04e1e6601c44b44e2237f2a97916a52ca9b156a820abdf6545547"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_multixact_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in multixacts) that a table's pg_class . relminmxid field can attain before a VACUUM operation is forced to prevent multixact ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuuming multixacts also allows removal of old files from the pg_multixact/members and pg_multixact/offsets subdirectories, which is why the default is a relatively low 400 million multixacts. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 25.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_max_age = value)", "description": ["Per-table value for autovacuum_multixact_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "17": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-max-age/?v=17", "label": "Table option autovacuum_multixact_freeze_max_age"}, {"url": "/docs/guc/autovacuum_multixact_freeze_max_age/?v=17", "label": "Global parameter autovacuum_multixact_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-autovacuum.html#GUC-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_multixact_freeze_max_age", "sha256": "8caf714d72c9f2ed5f0f8d65041109e0ab8845c7c1169c0febef5193bdaef36d"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_multixact_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in multixacts) that a table's pg_class . relminmxid field can attain before a VACUUM operation is forced to prevent multixact ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuuming multixacts also allows removal of old files from the pg_multixact/members and pg_multixact/offsets subdirectories, which is why the default is a relatively low 400 million multixacts. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_max_age = value)", "description": ["Per-table value for autovacuum_multixact_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "18": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-max-age/?v=18", "label": "Table option autovacuum_multixact_freeze_max_age"}, {"url": "/docs/guc/autovacuum_multixact_freeze_max_age/?v=18", "label": "Global parameter autovacuum_multixact_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_multixact_freeze_max_age", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_multixact_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in multixacts) that a table's pg_class . relminmxid field can attain before a VACUUM operation is forced to prevent multixact ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuuming multixacts also allows removal of old files from the pg_multixact/members and pg_multixact/offsets subdirectories, which is why the default is a relatively low 400 million multixacts. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_max_age = value)", "description": ["Per-table value for autovacuum_multixact_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "19": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-max-age/?v=19", "label": "Table option autovacuum_multixact_freeze_max_age"}, {"url": "/docs/guc/autovacuum_multixact_freeze_max_age/?v=19", "label": "Global parameter autovacuum_multixact_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_multixact_freeze_max_age", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_multixact_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in multixacts) that a table's pg_class . relminmxid field can attain before a VACUUM operation is forced to prevent multixact ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuuming multixacts also allows removal of old files from the pg_multixact/members and pg_multixact/offsets subdirectories, which is why the default is a relatively low 400 million multixacts. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_max_age = value)", "description": ["Per-table value for autovacuum_multixact_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "20": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-max-age/?v=20", "label": "Table option autovacuum_multixact_freeze_max_age"}, {"url": "/docs/guc/autovacuum_multixact_freeze_max_age/?v=20", "label": "Global parameter autovacuum_multixact_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_multixact_freeze_max_age", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_multixact_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in multixacts) that a table's pg_class . relminmxid field can attain before a VACUUM operation is forced to prevent multixact ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuuming multixacts also allows removal of old files from the pg_multixact/members and pg_multixact/offsets subdirectories, which is why the default is a relatively low 400 million multixacts. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_max_age = value)", "description": ["Per-table value for autovacuum_multixact_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}}, "content_hash": "34eadf4d5477b69ab6648869f8e87e7e5e3088eddf0b4cf80030893ba101545b", "imported_at": "2026-09-27T09:57:58.992", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-max-age/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-max-age/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-max-age/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-max-age/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-max-age/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-max-age/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-max-age/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-max-age/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-max-age/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-max-age/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-max-age/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-max-age/?v=20"}], "present": true}, {"slug": "toast-autovacuum-multixact-freeze-min-age", "name": "toast.autovacuum_multixact_freeze_min_age", "name_zh": "TOAST autovacuum_multixact_freeze_min_age", "category": "TOAST tables", "summary": "Per-table value for vacuum_multixact_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_min_age parameters that are larger than half the system-wide autovacuum_multixact_freeze_max_age setting.", "aliases": ["autovacuum_multixact_freeze_min_age"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-min-age/?v=10", "label": "Table option autovacuum_multixact_freeze_min_age"}, {"url": "/docs/guc/vacuum_multixact_freeze_min_age/?v=10", "label": "Global parameter vacuum_multixact_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_min_age", "sha256": "81c199a46b03a65a060e25cf874fc7ddd28b18261a6472a912954073556935b4"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in multixacts) that VACUUM should use to decide whether to replace multixact IDs with a newer transaction ID or multixact ID while scanning a table. The default is 5 million multixacts. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_multixact_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_min_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_min_age parameters that are larger than half the system-wide autovacuum_multixact_freeze_max_age setting."]}, "11": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-min-age/?v=11", "label": "Table option autovacuum_multixact_freeze_min_age"}, {"url": "/docs/guc/vacuum_multixact_freeze_min_age/?v=11", "label": "Global parameter vacuum_multixact_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_min_age", "sha256": "488947b3f6c09ac9a815b8602e852239936b403ef214249fee7aeca1469c25ba"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in multixacts) that VACUUM should use to decide whether to replace multixact IDs with a newer transaction ID or multixact ID while scanning a table. The default is 5 million multixacts. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_multixact_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_min_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_min_age parameters that are larger than half the system-wide autovacuum_multixact_freeze_max_age setting."]}, "12": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-min-age/?v=12", "label": "Table option autovacuum_multixact_freeze_min_age"}, {"url": "/docs/guc/vacuum_multixact_freeze_min_age/?v=12", "label": "Global parameter vacuum_multixact_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_min_age", "sha256": "7f27882cdde3b36cef070cdd14ce3f080b65ed837d3f6b41f3faf454ba89cc63"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in multixacts) that VACUUM should use to decide whether to replace multixact IDs with a newer transaction ID or multixact ID while scanning a table. The default is 5 million multixacts. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_multixact_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_min_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_min_age parameters that are larger than half the system-wide autovacuum_multixact_freeze_max_age setting."]}, "13": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-min-age/?v=13", "label": "Table option autovacuum_multixact_freeze_min_age"}, {"url": "/docs/guc/vacuum_multixact_freeze_min_age/?v=13", "label": "Global parameter vacuum_multixact_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_min_age", "sha256": "5d70022f2524a39e7c5745698de51d867f687c70394779ad154e05648e923c7d"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in multixacts) that VACUUM should use to decide whether to replace multixact IDs with a newer transaction ID or multixact ID while scanning a table. The default is 5 million multixacts. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_multixact_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_min_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_min_age parameters that are larger than half the system-wide autovacuum_multixact_freeze_max_age setting."]}, "14": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-min-age/?v=14", "label": "Table option autovacuum_multixact_freeze_min_age"}, {"url": "/docs/guc/vacuum_multixact_freeze_min_age/?v=14", "label": "Global parameter vacuum_multixact_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_min_age", "sha256": "35d48bb20f151039202a7cafbe7c4ffb109262110d62b2ab75844a3d80c2cebb"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in multixacts) that VACUUM should use to decide whether to replace multixact IDs with a newer transaction ID or multixact ID while scanning a table. The default is 5 million multixacts. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_multixact_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 25.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_min_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_min_age parameters that are larger than half the system-wide autovacuum_multixact_freeze_max_age setting."]}, "15": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-min-age/?v=15", "label": "Table option autovacuum_multixact_freeze_min_age"}, {"url": "/docs/guc/vacuum_multixact_freeze_min_age/?v=15", "label": "Global parameter vacuum_multixact_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_min_age", "sha256": "fdcf588ddeeac62758840aa3b8d6ead7e37e1b0c72795e339f67db5b23509462"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in multixacts) that VACUUM should use to decide whether to replace multixact IDs with a newer transaction ID or multixact ID while scanning a table. The default is 5 million multixacts. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_multixact_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 25.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_min_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_min_age parameters that are larger than half the system-wide autovacuum_multixact_freeze_max_age setting."]}, "16": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-min-age/?v=16", "label": "Table option autovacuum_multixact_freeze_min_age"}, {"url": "/docs/guc/vacuum_multixact_freeze_min_age/?v=16", "label": "Global parameter vacuum_multixact_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_min_age", "sha256": "e7e096464bd87b0bfc06652cdbbdd175f7a0e955207580049eae2ee394566b20"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in multixacts) that VACUUM should use to decide whether to trigger freezing of pages with an older multixact ID. The default is 5 million multixacts. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_multixact_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 25.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_min_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_min_age parameters that are larger than half the system-wide autovacuum_multixact_freeze_max_age setting."]}, "17": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-min-age/?v=17", "label": "Table option autovacuum_multixact_freeze_min_age"}, {"url": "/docs/guc/vacuum_multixact_freeze_min_age/?v=17", "label": "Global parameter vacuum_multixact_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_min_age", "sha256": "e7ba41a33997d251c23f06ccf17978bf1481db92a2c607026f59af86c25d6f50"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in multixacts) that VACUUM should use to decide whether to trigger freezing of pages with an older multixact ID. The default is 5 million multixacts. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_multixact_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_min_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_min_age parameters that are larger than half the system-wide autovacuum_multixact_freeze_max_age setting."]}, "18": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-min-age/?v=18", "label": "Table option autovacuum_multixact_freeze_min_age"}, {"url": "/docs/guc/vacuum_multixact_freeze_min_age/?v=18", "label": "Global parameter vacuum_multixact_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-VACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_multixact_freeze_min_age", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in multixacts) that VACUUM should use to decide whether to trigger freezing of pages with an older multixact ID. The default is 5 million multixacts. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_multixact_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_min_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_min_age parameters that are larger than half the system-wide autovacuum_multixact_freeze_max_age setting."]}, "19": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-min-age/?v=19", "label": "Table option autovacuum_multixact_freeze_min_age"}, {"url": "/docs/guc/vacuum_multixact_freeze_min_age/?v=19", "label": "Global parameter vacuum_multixact_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-VACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_multixact_freeze_min_age", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in multixacts) that VACUUM should use to decide whether to trigger freezing of pages with an older multixact ID. The default is 5 million multixacts. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_multixact_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_min_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_min_age parameters that are larger than half the system-wide autovacuum_multixact_freeze_max_age setting."]}, "20": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-min-age/?v=20", "label": "Table option autovacuum_multixact_freeze_min_age"}, {"url": "/docs/guc/vacuum_multixact_freeze_min_age/?v=20", "label": "Global parameter vacuum_multixact_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-VACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_multixact_freeze_min_age", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in multixacts) that VACUUM should use to decide whether to trigger freezing of pages with an older multixact ID. The default is 5 million multixacts. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_multixact_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_min_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_min_age parameters that are larger than half the system-wide autovacuum_multixact_freeze_max_age setting."]}}, "content_hash": "b2494aab08466042a76b727809bc408ee0bdb567bb09c6706d9c4b76a38db864", "imported_at": "2026-09-27T09:57:58.995", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-min-age/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-min-age/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-min-age/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-min-age/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-min-age/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-min-age/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-min-age/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-min-age/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-min-age/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-min-age/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-min-age/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-min-age/?v=20"}], "present": true}, {"slug": "toast-autovacuum-multixact-freeze-table-age", "name": "toast.autovacuum_multixact_freeze_table_age", "name_zh": "TOAST autovacuum_multixact_freeze_table_age", "category": "TOAST tables", "summary": "Per-table value for vacuum_multixact_freeze_table_age parameter.", "aliases": ["autovacuum_multixact_freeze_table_age"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-table-age/?v=10", "label": "Table option autovacuum_multixact_freeze_table_age"}, {"url": "/docs/guc/vacuum_multixact_freeze_table_age/?v=10", "label": "Global parameter vacuum_multixact_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_table_age", "sha256": "81c199a46b03a65a060e25cf874fc7ddd28b18261a6472a912954073556935b4"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relminmxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million multixacts. Although users can set this value anywhere from zero to two billions, VACUUM will silently limit the effective value to 95% of autovacuum_multixact_freeze_max_age , so that a periodical manual VACUUM has a chance to run before an anti-wraparound is launched for the table. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_table_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_table_age parameter."]}, "11": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-table-age/?v=11", "label": "Table option autovacuum_multixact_freeze_table_age"}, {"url": "/docs/guc/vacuum_multixact_freeze_table_age/?v=11", "label": "Global parameter vacuum_multixact_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_table_age", "sha256": "488947b3f6c09ac9a815b8602e852239936b403ef214249fee7aeca1469c25ba"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relminmxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million multixacts. Although users can set this value anywhere from zero to two billions, VACUUM will silently limit the effective value to 95% of autovacuum_multixact_freeze_max_age , so that a periodical manual VACUUM has a chance to run before an anti-wraparound is launched for the table. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_table_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_table_age parameter."]}, "12": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-table-age/?v=12", "label": "Table option autovacuum_multixact_freeze_table_age"}, {"url": "/docs/guc/vacuum_multixact_freeze_table_age/?v=12", "label": "Global parameter vacuum_multixact_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_table_age", "sha256": "7f27882cdde3b36cef070cdd14ce3f080b65ed837d3f6b41f3faf454ba89cc63"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relminmxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million multixacts. Although users can set this value anywhere from zero to two billions, VACUUM will silently limit the effective value to 95% of autovacuum_multixact_freeze_max_age , so that a periodical manual VACUUM has a chance to run before an anti-wraparound is launched for the table. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_table_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_table_age parameter."]}, "13": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-table-age/?v=13", "label": "Table option autovacuum_multixact_freeze_table_age"}, {"url": "/docs/guc/vacuum_multixact_freeze_table_age/?v=13", "label": "Global parameter vacuum_multixact_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_table_age", "sha256": "5d70022f2524a39e7c5745698de51d867f687c70394779ad154e05648e923c7d"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relminmxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million multixacts. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_multixact_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound is launched for the table. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_table_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_table_age parameter."]}, "14": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-table-age/?v=14", "label": "Table option autovacuum_multixact_freeze_table_age"}, {"url": "/docs/guc/vacuum_multixact_freeze_table_age/?v=14", "label": "Global parameter vacuum_multixact_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_table_age", "sha256": "35d48bb20f151039202a7cafbe7c4ffb109262110d62b2ab75844a3d80c2cebb"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relminmxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million multixacts. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_multixact_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound is launched for the table. For more information see Section 25.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_table_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_table_age parameter."]}, "15": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-table-age/?v=15", "label": "Table option autovacuum_multixact_freeze_table_age"}, {"url": "/docs/guc/vacuum_multixact_freeze_table_age/?v=15", "label": "Global parameter vacuum_multixact_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_table_age", "sha256": "fdcf588ddeeac62758840aa3b8d6ead7e37e1b0c72795e339f67db5b23509462"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relminmxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million multixacts. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_multixact_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound is launched for the table. For more information see Section 25.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_table_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_table_age parameter."]}, "16": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-table-age/?v=16", "label": "Table option autovacuum_multixact_freeze_table_age"}, {"url": "/docs/guc/vacuum_multixact_freeze_table_age/?v=16", "label": "Global parameter vacuum_multixact_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_table_age", "sha256": "e7e096464bd87b0bfc06652cdbbdd175f7a0e955207580049eae2ee394566b20"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relminmxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million multixacts. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_multixact_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound is launched for the table. For more information see Section 25.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_table_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_table_age parameter."]}, "17": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-table-age/?v=17", "label": "Table option autovacuum_multixact_freeze_table_age"}, {"url": "/docs/guc/vacuum_multixact_freeze_table_age/?v=17", "label": "Global parameter vacuum_multixact_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_table_age", "sha256": "e7ba41a33997d251c23f06ccf17978bf1481db92a2c607026f59af86c25d6f50"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relminmxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million multixacts. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_multixact_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound is launched for the table. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_table_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_table_age parameter."]}, "18": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-table-age/?v=18", "label": "Table option autovacuum_multixact_freeze_table_age"}, {"url": "/docs/guc/vacuum_multixact_freeze_table_age/?v=18", "label": "Global parameter vacuum_multixact_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-VACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_multixact_freeze_table_age", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relminmxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million multixacts. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_multixact_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound is launched for the table. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_table_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_table_age parameter."]}, "19": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-table-age/?v=19", "label": "Table option autovacuum_multixact_freeze_table_age"}, {"url": "/docs/guc/vacuum_multixact_freeze_table_age/?v=19", "label": "Global parameter vacuum_multixact_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-VACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_multixact_freeze_table_age", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relminmxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million multixacts. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_multixact_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound is launched for the table. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_table_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_table_age parameter."]}, "20": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-multixact-freeze-table-age/?v=20", "label": "Table option autovacuum_multixact_freeze_table_age"}, {"url": "/docs/guc/vacuum_multixact_freeze_table_age/?v=20", "label": "Global parameter vacuum_multixact_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-VACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_multixact_freeze_table_age", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relminmxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million multixacts. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_multixact_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound is launched for the table. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (toast.autovacuum_multixact_freeze_table_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_table_age parameter."]}}, "content_hash": "d7a51f9d521ee4a43f27486c322b63023162884dd126b1c1a94ccad8be09727e", "imported_at": "2026-09-27T09:57:58.998", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-table-age/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-table-age/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-table-age/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-table-age/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-table-age/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-table-age/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-table-age/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-table-age/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-table-age/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-table-age/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-table-age/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-multixact-freeze-table-age/?v=20"}], "present": true}, {"slug": "toast-autovacuum-vacuum-cost-delay", "name": "toast.autovacuum_vacuum_cost_delay", "name_zh": "TOAST autovacuum_vacuum_cost_delay", "category": "TOAST tables", "summary": "Per-table value for autovacuum_vacuum_cost_delay parameter.", "aliases": ["autovacuum_vacuum_cost_delay"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-cost-delay/?v=10", "label": "Table option autovacuum_vacuum_cost_delay"}, {"url": "/docs/guc/autovacuum_vacuum_cost_delay/?v=10", "label": "Global parameter autovacuum_vacuum_cost_delay"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_delay", "sha256": "a8c8d51fd43c0e169a2ce6bcb094c1dbd5f0f6cd6e90cabc86f6542039600355"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_delay", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost delay value that will be used in automatic VACUUM operations. If -1 is specified, the regular vacuum_cost_delay value will be used. The default value is 20 milliseconds. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_cost_delay = value)", "description": ["Per-table value for autovacuum_vacuum_cost_delay parameter."]}, "11": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-cost-delay/?v=11", "label": "Table option autovacuum_vacuum_cost_delay"}, {"url": "/docs/guc/autovacuum_vacuum_cost_delay/?v=11", "label": "Global parameter autovacuum_vacuum_cost_delay"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_delay", "sha256": "a553adbaa0edb4dbdf216a59031edf5974a2791c02e12f3a6f23a0df0cdc59d1"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_delay", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost delay value that will be used in automatic VACUUM operations. If -1 is specified, the regular vacuum_cost_delay value will be used. The default value is 20 milliseconds. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_cost_delay = value)", "description": ["Per-table value for autovacuum_vacuum_cost_delay parameter."]}, "12": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-cost-delay/?v=12", "label": "Table option autovacuum_vacuum_cost_delay"}, {"url": "/docs/guc/autovacuum_vacuum_cost_delay/?v=12", "label": "Global parameter autovacuum_vacuum_cost_delay"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-DELAY", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_delay", "sha256": "bb486d78e8d17e633e046674781b62e0cf0f77efbb48cd6fffa5fd6b34ac98e6"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_delay", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost delay value that will be used in automatic VACUUM operations. If -1 is specified, the regular vacuum_cost_delay value will be used. If this value is specified without units, it is taken as milliseconds. The default value is 2 milliseconds. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_cost_delay = value)", "description": ["Per-table value for autovacuum_vacuum_cost_delay parameter."]}, "13": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-cost-delay/?v=13", "label": "Table option autovacuum_vacuum_cost_delay"}, {"url": "/docs/guc/autovacuum_vacuum_cost_delay/?v=13", "label": "Global parameter autovacuum_vacuum_cost_delay"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-DELAY", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_delay", "sha256": "d26d014ad3850d3dbbbc1bce41bc267205baa1523b73e48fdd9e7165b6f6785e"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_delay", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost delay value that will be used in automatic VACUUM operations. If -1 is specified, the regular vacuum_cost_delay value will be used. If this value is specified without units, it is taken as milliseconds. The default value is 2 milliseconds. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_cost_delay = value)", "description": ["Per-table value for autovacuum_vacuum_cost_delay parameter."]}, "14": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-cost-delay/?v=14", "label": "Table option autovacuum_vacuum_cost_delay"}, {"url": "/docs/guc/autovacuum_vacuum_cost_delay/?v=14", "label": "Global parameter autovacuum_vacuum_cost_delay"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-DELAY", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_delay", "sha256": "03e821969b789b688f725579aa8bd52763880e798ca8680d894f2c12861724cf"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_delay", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost delay value that will be used in automatic VACUUM operations. If -1 is specified, the regular vacuum_cost_delay value will be used. If this value is specified without units, it is taken as milliseconds. The default value is 2 milliseconds. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_cost_delay = value)", "description": ["Per-table value for autovacuum_vacuum_cost_delay parameter."]}, "15": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-cost-delay/?v=15", "label": "Table option autovacuum_vacuum_cost_delay"}, {"url": "/docs/guc/autovacuum_vacuum_cost_delay/?v=15", "label": "Global parameter autovacuum_vacuum_cost_delay"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-DELAY", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_delay", "sha256": "993bb5fe87856e4c4cb9aedac41232b5915272a65226f57e7fbf0713be2b13f4"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_delay", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost delay value that will be used in automatic VACUUM operations. If -1 is specified, the regular vacuum_cost_delay value will be used. If this value is specified without units, it is taken as milliseconds. The default value is 2 milliseconds. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_cost_delay = value)", "description": ["Per-table value for autovacuum_vacuum_cost_delay parameter."]}, "16": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-cost-delay/?v=16", "label": "Table option autovacuum_vacuum_cost_delay"}, {"url": "/docs/guc/autovacuum_vacuum_cost_delay/?v=16", "label": "Global parameter autovacuum_vacuum_cost_delay"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-DELAY", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_delay", "sha256": "b16c76b3ffb04e1e6601c44b44e2237f2a97916a52ca9b156a820abdf6545547"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_delay", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost delay value that will be used in automatic VACUUM operations. If -1 is specified, the regular vacuum_cost_delay value will be used. If this value is specified without units, it is taken as milliseconds. The default value is 2 milliseconds. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_cost_delay = value)", "description": ["Per-table value for autovacuum_vacuum_cost_delay parameter."]}, "17": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-cost-delay/?v=17", "label": "Table option autovacuum_vacuum_cost_delay"}, {"url": "/docs/guc/autovacuum_vacuum_cost_delay/?v=17", "label": "Global parameter autovacuum_vacuum_cost_delay"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-DELAY", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_delay", "sha256": "8caf714d72c9f2ed5f0f8d65041109e0ab8845c7c1169c0febef5193bdaef36d"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_delay", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost delay value that will be used in automatic VACUUM operations. If -1 is specified, the regular vacuum_cost_delay value will be used. If this value is specified without units, it is taken as milliseconds. The default value is 2 milliseconds. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_cost_delay = value)", "description": ["Per-table value for autovacuum_vacuum_cost_delay parameter."]}, "18": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-cost-delay/?v=18", "label": "Table option autovacuum_vacuum_cost_delay"}, {"url": "/docs/guc/autovacuum_vacuum_cost_delay/?v=18", "label": "Global parameter autovacuum_vacuum_cost_delay"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-DELAY", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_delay", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_delay", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost delay value that will be used in automatic VACUUM operations. If -1 is specified, the regular vacuum_cost_delay value will be used. If this value is specified without units, it is taken as milliseconds. The default value is 2 milliseconds. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_cost_delay = value)", "description": ["Per-table value for autovacuum_vacuum_cost_delay parameter."]}, "19": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-cost-delay/?v=19", "label": "Table option autovacuum_vacuum_cost_delay"}, {"url": "/docs/guc/autovacuum_vacuum_cost_delay/?v=19", "label": "Global parameter autovacuum_vacuum_cost_delay"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-DELAY", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_delay", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_delay", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost delay value that will be used in automatic VACUUM operations. If -1 is specified, the regular vacuum_cost_delay value will be used. If this value is specified without units, it is taken as milliseconds. The default value is 2 milliseconds. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_cost_delay = value)", "description": ["Per-table value for autovacuum_vacuum_cost_delay parameter."]}, "20": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-cost-delay/?v=20", "label": "Table option autovacuum_vacuum_cost_delay"}, {"url": "/docs/guc/autovacuum_vacuum_cost_delay/?v=20", "label": "Global parameter autovacuum_vacuum_cost_delay"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-DELAY", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_delay", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_delay", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost delay value that will be used in automatic VACUUM operations. If -1 is specified, the regular vacuum_cost_delay value will be used. If this value is specified without units, it is taken as milliseconds. The default value is 2 milliseconds. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_cost_delay = value)", "description": ["Per-table value for autovacuum_vacuum_cost_delay parameter."]}}, "content_hash": "34d502b8f637c2b7e0284ccaed904e8add20198520355469d4f34b92195a113a", "imported_at": "2026-09-27T09:57:59.003", "url": "/wiki/relopts/toast-autovacuum-vacuum-cost-delay/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-cost-delay/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-cost-delay/?v=11"}, {"major": "12", "state": "changed", "label": "Interface or attribute change", "title": "PostgreSQL 12.22 \u00b7 Interface or attribute change", "url": "/wiki/relopts/toast-autovacuum-vacuum-cost-delay/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-cost-delay/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-cost-delay/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-cost-delay/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-cost-delay/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-cost-delay/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-cost-delay/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-cost-delay/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-cost-delay/?v=20"}], "present": true}, {"slug": "toast-autovacuum-vacuum-cost-limit", "name": "toast.autovacuum_vacuum_cost_limit", "name_zh": "TOAST autovacuum_vacuum_cost_limit", "category": "TOAST tables", "summary": "Per-table value for autovacuum_vacuum_cost_limit parameter.", "aliases": ["autovacuum_vacuum_cost_limit"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-cost-limit/?v=10", "label": "Table option autovacuum_vacuum_cost_limit"}, {"url": "/docs/guc/autovacuum_vacuum_cost_limit/?v=10", "label": "Global parameter autovacuum_vacuum_cost_limit"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_limit", "sha256": "a8c8d51fd43c0e169a2ce6bcb094c1dbd5f0f6cd6e90cabc86f6542039600355"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost limit value that will be used in automatic VACUUM operations. If -1 is specified (which is the default), the regular vacuum_cost_limit value will be used. Note that the value is distributed proportionally among the running autovacuum workers, if there is more than one, so that the sum of the limits for each worker does not exceed the value of this variable. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_cost_limit = value)", "description": ["Per-table value for autovacuum_vacuum_cost_limit parameter."]}, "11": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-cost-limit/?v=11", "label": "Table option autovacuum_vacuum_cost_limit"}, {"url": "/docs/guc/autovacuum_vacuum_cost_limit/?v=11", "label": "Global parameter autovacuum_vacuum_cost_limit"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_limit", "sha256": "a553adbaa0edb4dbdf216a59031edf5974a2791c02e12f3a6f23a0df0cdc59d1"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost limit value that will be used in automatic VACUUM operations. If -1 is specified (which is the default), the regular vacuum_cost_limit value will be used. Note that the value is distributed proportionally among the running autovacuum workers, if there is more than one, so that the sum of the limits for each worker does not exceed the value of this variable. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_cost_limit = value)", "description": ["Per-table value for autovacuum_vacuum_cost_limit parameter."]}, "12": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-cost-limit/?v=12", "label": "Table option autovacuum_vacuum_cost_limit"}, {"url": "/docs/guc/autovacuum_vacuum_cost_limit/?v=12", "label": "Global parameter autovacuum_vacuum_cost_limit"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_limit", "sha256": "bb486d78e8d17e633e046674781b62e0cf0f77efbb48cd6fffa5fd6b34ac98e6"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost limit value that will be used in automatic VACUUM operations. If -1 is specified (which is the default), the regular vacuum_cost_limit value will be used. Note that the value is distributed proportionally among the running autovacuum workers, if there is more than one, so that the sum of the limits for each worker does not exceed the value of this variable. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_cost_limit = value)", "description": ["Per-table value for autovacuum_vacuum_cost_limit parameter."]}, "13": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-cost-limit/?v=13", "label": "Table option autovacuum_vacuum_cost_limit"}, {"url": "/docs/guc/autovacuum_vacuum_cost_limit/?v=13", "label": "Global parameter autovacuum_vacuum_cost_limit"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_limit", "sha256": "d26d014ad3850d3dbbbc1bce41bc267205baa1523b73e48fdd9e7165b6f6785e"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost limit value that will be used in automatic VACUUM operations. If -1 is specified (which is the default), the regular vacuum_cost_limit value will be used. Note that the value is distributed proportionally among the running autovacuum workers, if there is more than one, so that the sum of the limits for each worker does not exceed the value of this variable. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_cost_limit = value)", "description": ["Per-table value for autovacuum_vacuum_cost_limit parameter."]}, "14": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-cost-limit/?v=14", "label": "Table option autovacuum_vacuum_cost_limit"}, {"url": "/docs/guc/autovacuum_vacuum_cost_limit/?v=14", "label": "Global parameter autovacuum_vacuum_cost_limit"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_limit", "sha256": "03e821969b789b688f725579aa8bd52763880e798ca8680d894f2c12861724cf"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost limit value that will be used in automatic VACUUM operations. If -1 is specified (which is the default), the regular vacuum_cost_limit value will be used. Note that the value is distributed proportionally among the running autovacuum workers, if there is more than one, so that the sum of the limits for each worker does not exceed the value of this variable. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_cost_limit = value)", "description": ["Per-table value for autovacuum_vacuum_cost_limit parameter."]}, "15": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-cost-limit/?v=15", "label": "Table option autovacuum_vacuum_cost_limit"}, {"url": "/docs/guc/autovacuum_vacuum_cost_limit/?v=15", "label": "Global parameter autovacuum_vacuum_cost_limit"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_limit", "sha256": "993bb5fe87856e4c4cb9aedac41232b5915272a65226f57e7fbf0713be2b13f4"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost limit value that will be used in automatic VACUUM operations. If -1 is specified (which is the default), the regular vacuum_cost_limit value will be used. Note that the value is distributed proportionally among the running autovacuum workers, if there is more than one, so that the sum of the limits for each worker does not exceed the value of this variable. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_cost_limit = value)", "description": ["Per-table value for autovacuum_vacuum_cost_limit parameter."]}, "16": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-cost-limit/?v=16", "label": "Table option autovacuum_vacuum_cost_limit"}, {"url": "/docs/guc/autovacuum_vacuum_cost_limit/?v=16", "label": "Global parameter autovacuum_vacuum_cost_limit"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_limit", "sha256": "b16c76b3ffb04e1e6601c44b44e2237f2a97916a52ca9b156a820abdf6545547"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost limit value that will be used in automatic VACUUM operations. If -1 is specified (which is the default), the regular vacuum_cost_limit value will be used. Note that the value is distributed proportionally among the running autovacuum workers, if there is more than one, so that the sum of the limits for each worker does not exceed the value of this variable. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_cost_limit = value)", "description": ["Per-table value for autovacuum_vacuum_cost_limit parameter."]}, "17": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-cost-limit/?v=17", "label": "Table option autovacuum_vacuum_cost_limit"}, {"url": "/docs/guc/autovacuum_vacuum_cost_limit/?v=17", "label": "Global parameter autovacuum_vacuum_cost_limit"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_limit", "sha256": "8caf714d72c9f2ed5f0f8d65041109e0ab8845c7c1169c0febef5193bdaef36d"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost limit value that will be used in automatic VACUUM operations. If -1 is specified (which is the default), the regular vacuum_cost_limit value will be used. Note that the value is distributed proportionally among the running autovacuum workers, if there is more than one, so that the sum of the limits for each worker does not exceed the value of this variable. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_cost_limit = value)", "description": ["Per-table value for autovacuum_vacuum_cost_limit parameter."]}, "18": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-cost-limit/?v=18", "label": "Table option autovacuum_vacuum_cost_limit"}, {"url": "/docs/guc/autovacuum_vacuum_cost_limit/?v=18", "label": "Global parameter autovacuum_vacuum_cost_limit"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_limit", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost limit value that will be used in automatic VACUUM operations. If -1 is specified (which is the default), the regular vacuum_cost_limit value will be used. Note that the value is distributed proportionally among the running autovacuum workers, if there is more than one, so that the sum of the limits for each worker does not exceed the value of this variable. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_cost_limit = value)", "description": ["Per-table value for autovacuum_vacuum_cost_limit parameter."]}, "19": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-cost-limit/?v=19", "label": "Table option autovacuum_vacuum_cost_limit"}, {"url": "/docs/guc/autovacuum_vacuum_cost_limit/?v=19", "label": "Global parameter autovacuum_vacuum_cost_limit"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_limit", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost limit value that will be used in automatic VACUUM operations. If -1 is specified (which is the default), the regular vacuum_cost_limit value will be used. Note that the value is distributed proportionally among the running autovacuum workers, if there is more than one, so that the sum of the limits for each worker does not exceed the value of this variable. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_cost_limit = value)", "description": ["Per-table value for autovacuum_vacuum_cost_limit parameter."]}, "20": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-cost-limit/?v=20", "label": "Table option autovacuum_vacuum_cost_limit"}, {"url": "/docs/guc/autovacuum_vacuum_cost_limit/?v=20", "label": "Global parameter autovacuum_vacuum_cost_limit"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_limit", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost limit value that will be used in automatic VACUUM operations. If -1 is specified (which is the default), the regular vacuum_cost_limit value will be used. Note that the value is distributed proportionally among the running autovacuum workers, if there is more than one, so that the sum of the limits for each worker does not exceed the value of this variable. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_cost_limit = value)", "description": ["Per-table value for autovacuum_vacuum_cost_limit parameter."]}}, "content_hash": "08270883e08311f609c09ba65051f87fe3ae14af407e0b025cb8e16d62a1fbed", "imported_at": "2026-09-27T09:57:59.006", "url": "/wiki/relopts/toast-autovacuum-vacuum-cost-limit/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-cost-limit/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-cost-limit/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-cost-limit/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-cost-limit/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-cost-limit/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-cost-limit/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-cost-limit/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-cost-limit/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-cost-limit/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-cost-limit/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-cost-limit/?v=20"}], "present": true}, {"slug": "toast-autovacuum-vacuum-insert-scale-factor", "name": "toast.autovacuum_vacuum_insert_scale_factor", "name_zh": "TOAST autovacuum_vacuum_insert_scale_factor", "category": "TOAST tables", "summary": "Per-table value for autovacuum_vacuum_insert_scale_factor parameter.", "aliases": ["autovacuum_vacuum_insert_scale_factor"], "versions": {"13": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-insert-scale-factor/?v=13", "label": "Table option autovacuum_vacuum_insert_scale_factor"}, {"url": "/docs/guc/autovacuum_vacuum_insert_scale_factor/?v=13", "label": "Global parameter autovacuum_vacuum_insert_scale_factor"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "sha256": "d26d014ad3850d3dbbbc1bce41bc267205baa1523b73e48fdd9e7165b6f6785e"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_insert_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_insert_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_insert_scale_factor parameter."]}, "14": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-insert-scale-factor/?v=14", "label": "Table option autovacuum_vacuum_insert_scale_factor"}, {"url": "/docs/guc/autovacuum_vacuum_insert_scale_factor/?v=14", "label": "Global parameter autovacuum_vacuum_insert_scale_factor"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "sha256": "03e821969b789b688f725579aa8bd52763880e798ca8680d894f2c12861724cf"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_insert_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_insert_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_insert_scale_factor parameter."]}, "15": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-insert-scale-factor/?v=15", "label": "Table option autovacuum_vacuum_insert_scale_factor"}, {"url": "/docs/guc/autovacuum_vacuum_insert_scale_factor/?v=15", "label": "Global parameter autovacuum_vacuum_insert_scale_factor"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "sha256": "993bb5fe87856e4c4cb9aedac41232b5915272a65226f57e7fbf0713be2b13f4"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_insert_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_insert_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_insert_scale_factor parameter."]}, "16": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-insert-scale-factor/?v=16", "label": "Table option autovacuum_vacuum_insert_scale_factor"}, {"url": "/docs/guc/autovacuum_vacuum_insert_scale_factor/?v=16", "label": "Global parameter autovacuum_vacuum_insert_scale_factor"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "sha256": "b16c76b3ffb04e1e6601c44b44e2237f2a97916a52ca9b156a820abdf6545547"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_insert_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_insert_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_insert_scale_factor parameter."]}, "17": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-insert-scale-factor/?v=17", "label": "Table option autovacuum_vacuum_insert_scale_factor"}, {"url": "/docs/guc/autovacuum_vacuum_insert_scale_factor/?v=17", "label": "Global parameter autovacuum_vacuum_insert_scale_factor"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "sha256": "8caf714d72c9f2ed5f0f8d65041109e0ab8845c7c1169c0febef5193bdaef36d"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_insert_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_insert_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_insert_scale_factor parameter."]}, "18": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-insert-scale-factor/?v=18", "label": "Table option autovacuum_vacuum_insert_scale_factor"}, {"url": "/docs/guc/autovacuum_vacuum_insert_scale_factor/?v=18", "label": "Global parameter autovacuum_vacuum_insert_scale_factor"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the unfrozen pages in the table to add to autovacuum_vacuum_insert_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of unfrozen pages in table). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_insert_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_insert_scale_factor parameter."]}, "19": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-insert-scale-factor/?v=19", "label": "Table option autovacuum_vacuum_insert_scale_factor"}, {"url": "/docs/guc/autovacuum_vacuum_insert_scale_factor/?v=19", "label": "Global parameter autovacuum_vacuum_insert_scale_factor"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the unfrozen pages in the table to add to autovacuum_vacuum_insert_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of unfrozen pages in table). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_insert_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_insert_scale_factor parameter."]}, "20": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-insert-scale-factor/?v=20", "label": "Table option autovacuum_vacuum_insert_scale_factor"}, {"url": "/docs/guc/autovacuum_vacuum_insert_scale_factor/?v=20", "label": "Global parameter autovacuum_vacuum_insert_scale_factor"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the unfrozen pages in the table to add to autovacuum_vacuum_insert_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of unfrozen pages in table). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_insert_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_insert_scale_factor parameter."]}}, "content_hash": "495a2fb490d25c0fa1905dd373dc2fd263d9d74aa07c92686be8ee9392582fac", "imported_at": "2026-09-27T09:57:59.010", "url": "/wiki/relopts/toast-autovacuum-vacuum-insert-scale-factor/?v=18", "cells": [{"major": "10", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 10.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-autovacuum-vacuum-insert-scale-factor/?v=10"}, {"major": "11", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 11.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-autovacuum-vacuum-insert-scale-factor/?v=11"}, {"major": "12", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 12.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-autovacuum-vacuum-insert-scale-factor/?v=12"}, {"major": "13", "state": "added", "label": "First recorded in this sample", "title": "PostgreSQL 13.23 \u00b7 First recorded in this sample", "url": "/wiki/relopts/toast-autovacuum-vacuum-insert-scale-factor/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-insert-scale-factor/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-insert-scale-factor/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-insert-scale-factor/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-insert-scale-factor/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-insert-scale-factor/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-insert-scale-factor/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-insert-scale-factor/?v=20"}], "present": true}, {"slug": "toast-autovacuum-vacuum-insert-threshold", "name": "toast.autovacuum_vacuum_insert_threshold", "name_zh": "TOAST autovacuum_vacuum_insert_threshold", "category": "TOAST tables", "summary": "Per-table value for autovacuum_vacuum_insert_threshold parameter. The special value of -1 may be used to disable insert vacuums on the table.", "aliases": ["autovacuum_vacuum_insert_threshold"], "versions": {"13": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-insert-threshold/?v=13", "label": "Table option autovacuum_vacuum_insert_threshold"}, {"url": "/docs/guc/autovacuum_vacuum_insert_threshold/?v=13", "label": "Global parameter autovacuum_vacuum_insert_threshold"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_threshold", "sha256": "d26d014ad3850d3dbbbc1bce41bc267205baa1523b73e48fdd9e7165b6f6785e"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the number of inserted tuples needed to trigger a VACUUM in any one table. The default is 1000 tuples. If -1 is specified, autovacuum will not trigger a VACUUM operation on any tables based on the number of inserts. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_insert_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_insert_threshold parameter. The special value of -1 may be used to disable insert vacuums on the table."]}, "14": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-insert-threshold/?v=14", "label": "Table option autovacuum_vacuum_insert_threshold"}, {"url": "/docs/guc/autovacuum_vacuum_insert_threshold/?v=14", "label": "Global parameter autovacuum_vacuum_insert_threshold"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_threshold", "sha256": "03e821969b789b688f725579aa8bd52763880e798ca8680d894f2c12861724cf"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the number of inserted tuples needed to trigger a VACUUM in any one table. The default is 1000 tuples. If -1 is specified, autovacuum will not trigger a VACUUM operation on any tables based on the number of inserts. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_insert_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_insert_threshold parameter. The special value of -1 may be used to disable insert vacuums on the table."]}, "15": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-insert-threshold/?v=15", "label": "Table option autovacuum_vacuum_insert_threshold"}, {"url": "/docs/guc/autovacuum_vacuum_insert_threshold/?v=15", "label": "Global parameter autovacuum_vacuum_insert_threshold"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_threshold", "sha256": "993bb5fe87856e4c4cb9aedac41232b5915272a65226f57e7fbf0713be2b13f4"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the number of inserted tuples needed to trigger a VACUUM in any one table. The default is 1000 tuples. If -1 is specified, autovacuum will not trigger a VACUUM operation on any tables based on the number of inserts. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_insert_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_insert_threshold parameter. The special value of -1 may be used to disable insert vacuums on the table."]}, "16": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-insert-threshold/?v=16", "label": "Table option autovacuum_vacuum_insert_threshold"}, {"url": "/docs/guc/autovacuum_vacuum_insert_threshold/?v=16", "label": "Global parameter autovacuum_vacuum_insert_threshold"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_threshold", "sha256": "b16c76b3ffb04e1e6601c44b44e2237f2a97916a52ca9b156a820abdf6545547"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the number of inserted tuples needed to trigger a VACUUM in any one table. The default is 1000 tuples. If -1 is specified, autovacuum will not trigger a VACUUM operation on any tables based on the number of inserts. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_insert_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_insert_threshold parameter. The special value of -1 may be used to disable insert vacuums on the table."]}, "17": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-insert-threshold/?v=17", "label": "Table option autovacuum_vacuum_insert_threshold"}, {"url": "/docs/guc/autovacuum_vacuum_insert_threshold/?v=17", "label": "Global parameter autovacuum_vacuum_insert_threshold"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_threshold", "sha256": "8caf714d72c9f2ed5f0f8d65041109e0ab8845c7c1169c0febef5193bdaef36d"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the number of inserted tuples needed to trigger a VACUUM in any one table. The default is 1000 tuples. If -1 is specified, autovacuum will not trigger a VACUUM operation on any tables based on the number of inserts. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_insert_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_insert_threshold parameter. The special value of -1 may be used to disable insert vacuums on the table."]}, "18": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-insert-threshold/?v=18", "label": "Table option autovacuum_vacuum_insert_threshold"}, {"url": "/docs/guc/autovacuum_vacuum_insert_threshold/?v=18", "label": "Global parameter autovacuum_vacuum_insert_threshold"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_threshold", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the number of inserted tuples needed to trigger a VACUUM in any one table. The default is 1000 tuples. If -1 is specified, autovacuum will not trigger a VACUUM operation on any tables based on the number of inserts. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_insert_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_insert_threshold parameter. The special value of -1 may be used to disable insert vacuums on the table."]}, "19": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-insert-threshold/?v=19", "label": "Table option autovacuum_vacuum_insert_threshold"}, {"url": "/docs/guc/autovacuum_vacuum_insert_threshold/?v=19", "label": "Global parameter autovacuum_vacuum_insert_threshold"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_threshold", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the number of inserted tuples needed to trigger a VACUUM in any one table. The default is 1000 tuples. If -1 is specified, autovacuum will not trigger a VACUUM operation on any tables based on the number of inserts. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_insert_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_insert_threshold parameter. The special value of -1 may be used to disable insert vacuums on the table."]}, "20": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-insert-threshold/?v=20", "label": "Table option autovacuum_vacuum_insert_threshold"}, {"url": "/docs/guc/autovacuum_vacuum_insert_threshold/?v=20", "label": "Global parameter autovacuum_vacuum_insert_threshold"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_threshold", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the number of inserted tuples needed to trigger a VACUUM in any one table. The default is 1000 tuples. If -1 is specified, autovacuum will not trigger a VACUUM operation on any tables based on the number of inserts. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_insert_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_insert_threshold parameter. The special value of -1 may be used to disable insert vacuums on the table."]}}, "content_hash": "1f2d37ac449570517c338fcb13c72abb8b7d050d1f3d73c57d4125966241fd0d", "imported_at": "2026-09-27T09:57:59.012", "url": "/wiki/relopts/toast-autovacuum-vacuum-insert-threshold/?v=18", "cells": [{"major": "10", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 10.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-autovacuum-vacuum-insert-threshold/?v=10"}, {"major": "11", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 11.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-autovacuum-vacuum-insert-threshold/?v=11"}, {"major": "12", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 12.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-autovacuum-vacuum-insert-threshold/?v=12"}, {"major": "13", "state": "added", "label": "First recorded in this sample", "title": "PostgreSQL 13.23 \u00b7 First recorded in this sample", "url": "/wiki/relopts/toast-autovacuum-vacuum-insert-threshold/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-insert-threshold/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-insert-threshold/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-insert-threshold/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-insert-threshold/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-insert-threshold/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-insert-threshold/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-insert-threshold/?v=20"}], "present": true}, {"slug": "toast-autovacuum-vacuum-max-threshold", "name": "toast.autovacuum_vacuum_max_threshold", "name_zh": "TOAST autovacuum_vacuum_max_threshold", "category": "TOAST tables", "summary": "Per-table value for autovacuum_vacuum_max_threshold parameter.", "aliases": ["autovacuum_vacuum_max_threshold"], "versions": {"18": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-max-threshold/?v=18", "label": "Table option autovacuum_vacuum_max_threshold"}, {"url": "/docs/guc/autovacuum_vacuum_max_threshold/?v=18", "label": "Global parameter autovacuum_vacuum_max_threshold"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-MAX-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-MAX-THRESHOLD", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_max_threshold", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_max_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum number of updated or deleted tuples needed to trigger a VACUUM in any one table, i.e., a limit on the value calculated with autovacuum_vacuum_threshold and autovacuum_vacuum_scale_factor . The default is 100,000,000 tuples. If -1 is specified, autovacuum will not enforce a maximum number of updated or deleted tuples that will trigger a VACUUM operation. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_max_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_max_threshold parameter."]}, "19": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-max-threshold/?v=19", "label": "Table option autovacuum_vacuum_max_threshold"}, {"url": "/docs/guc/autovacuum_vacuum_max_threshold/?v=19", "label": "Global parameter autovacuum_vacuum_max_threshold"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-MAX-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-MAX-THRESHOLD", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_max_threshold", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_max_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum number of updated or deleted tuples needed to trigger a VACUUM in any one table, i.e., a limit on the value calculated with autovacuum_vacuum_threshold and autovacuum_vacuum_scale_factor . The default is 100,000,000 tuples. If -1 is specified, autovacuum will not enforce a maximum number of updated or deleted tuples that will trigger a VACUUM operation. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_max_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_max_threshold parameter."]}, "20": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-max-threshold/?v=20", "label": "Table option autovacuum_vacuum_max_threshold"}, {"url": "/docs/guc/autovacuum_vacuum_max_threshold/?v=20", "label": "Global parameter autovacuum_vacuum_max_threshold"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-MAX-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-MAX-THRESHOLD", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_max_threshold", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_max_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum number of updated or deleted tuples needed to trigger a VACUUM in any one table, i.e., a limit on the value calculated with autovacuum_vacuum_threshold and autovacuum_vacuum_scale_factor . The default is 100,000,000 tuples. If -1 is specified, autovacuum will not enforce a maximum number of updated or deleted tuples that will trigger a VACUUM operation. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_max_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_max_threshold parameter."]}}, "content_hash": "54485fa2ba71ba4f4088cf1d221719033b62a73c0fb70025c833c3d6ffac80eb", "imported_at": "2026-09-27T09:57:59.015", "url": "/wiki/relopts/toast-autovacuum-vacuum-max-threshold/?v=18", "cells": [{"major": "10", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 10.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-autovacuum-vacuum-max-threshold/?v=10"}, {"major": "11", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 11.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-autovacuum-vacuum-max-threshold/?v=11"}, {"major": "12", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 12.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-autovacuum-vacuum-max-threshold/?v=12"}, {"major": "13", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 13.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-autovacuum-vacuum-max-threshold/?v=13"}, {"major": "14", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 14.24 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-autovacuum-vacuum-max-threshold/?v=14"}, {"major": "15", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 15.19 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-autovacuum-vacuum-max-threshold/?v=15"}, {"major": "16", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 16.15 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-autovacuum-vacuum-max-threshold/?v=16"}, {"major": "17", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 17.11 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-autovacuum-vacuum-max-threshold/?v=17"}, {"major": "18", "state": "added", "label": "First recorded in this sample", "title": "PostgreSQL 18.6 \u00b7 First recorded in this sample", "url": "/wiki/relopts/toast-autovacuum-vacuum-max-threshold/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-max-threshold/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-max-threshold/?v=20"}], "present": true}, {"slug": "toast-autovacuum-vacuum-scale-factor", "name": "toast.autovacuum_vacuum_scale_factor", "name_zh": "TOAST autovacuum_vacuum_scale_factor", "category": "TOAST tables", "summary": "Per-table value for autovacuum_vacuum_scale_factor parameter.", "aliases": ["autovacuum_vacuum_scale_factor"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-scale-factor/?v=10", "label": "Table option autovacuum_vacuum_scale_factor"}, {"url": "/docs/guc/autovacuum_vacuum_scale_factor/?v=10", "label": "Global parameter autovacuum_vacuum_scale_factor"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_scale_factor", "sha256": "a8c8d51fd43c0e169a2ce6bcb094c1dbd5f0f6cd6e90cabc86f6542039600355"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_scale_factor parameter."]}, "11": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-scale-factor/?v=11", "label": "Table option autovacuum_vacuum_scale_factor"}, {"url": "/docs/guc/autovacuum_vacuum_scale_factor/?v=11", "label": "Global parameter autovacuum_vacuum_scale_factor"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_scale_factor", "sha256": "a553adbaa0edb4dbdf216a59031edf5974a2791c02e12f3a6f23a0df0cdc59d1"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_scale_factor parameter."]}, "12": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-scale-factor/?v=12", "label": "Table option autovacuum_vacuum_scale_factor"}, {"url": "/docs/guc/autovacuum_vacuum_scale_factor/?v=12", "label": "Global parameter autovacuum_vacuum_scale_factor"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_scale_factor", "sha256": "bb486d78e8d17e633e046674781b62e0cf0f77efbb48cd6fffa5fd6b34ac98e6"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_scale_factor parameter."]}, "13": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-scale-factor/?v=13", "label": "Table option autovacuum_vacuum_scale_factor"}, {"url": "/docs/guc/autovacuum_vacuum_scale_factor/?v=13", "label": "Global parameter autovacuum_vacuum_scale_factor"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_scale_factor", "sha256": "d26d014ad3850d3dbbbc1bce41bc267205baa1523b73e48fdd9e7165b6f6785e"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_scale_factor parameter."]}, "14": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-scale-factor/?v=14", "label": "Table option autovacuum_vacuum_scale_factor"}, {"url": "/docs/guc/autovacuum_vacuum_scale_factor/?v=14", "label": "Global parameter autovacuum_vacuum_scale_factor"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_scale_factor", "sha256": "03e821969b789b688f725579aa8bd52763880e798ca8680d894f2c12861724cf"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_scale_factor parameter."]}, "15": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-scale-factor/?v=15", "label": "Table option autovacuum_vacuum_scale_factor"}, {"url": "/docs/guc/autovacuum_vacuum_scale_factor/?v=15", "label": "Global parameter autovacuum_vacuum_scale_factor"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_scale_factor", "sha256": "993bb5fe87856e4c4cb9aedac41232b5915272a65226f57e7fbf0713be2b13f4"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_scale_factor parameter."]}, "16": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-scale-factor/?v=16", "label": "Table option autovacuum_vacuum_scale_factor"}, {"url": "/docs/guc/autovacuum_vacuum_scale_factor/?v=16", "label": "Global parameter autovacuum_vacuum_scale_factor"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_scale_factor", "sha256": "b16c76b3ffb04e1e6601c44b44e2237f2a97916a52ca9b156a820abdf6545547"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_scale_factor parameter."]}, "17": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-scale-factor/?v=17", "label": "Table option autovacuum_vacuum_scale_factor"}, {"url": "/docs/guc/autovacuum_vacuum_scale_factor/?v=17", "label": "Global parameter autovacuum_vacuum_scale_factor"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_scale_factor", "sha256": "8caf714d72c9f2ed5f0f8d65041109e0ab8845c7c1169c0febef5193bdaef36d"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_scale_factor parameter."]}, "18": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-scale-factor/?v=18", "label": "Table option autovacuum_vacuum_scale_factor"}, {"url": "/docs/guc/autovacuum_vacuum_scale_factor/?v=18", "label": "Global parameter autovacuum_vacuum_scale_factor"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_scale_factor", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_scale_factor parameter."]}, "19": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-scale-factor/?v=19", "label": "Table option autovacuum_vacuum_scale_factor"}, {"url": "/docs/guc/autovacuum_vacuum_scale_factor/?v=19", "label": "Global parameter autovacuum_vacuum_scale_factor"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_scale_factor", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_scale_factor parameter."]}, "20": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-scale-factor/?v=20", "label": "Table option autovacuum_vacuum_scale_factor"}, {"url": "/docs/guc/autovacuum_vacuum_scale_factor/?v=20", "label": "Global parameter autovacuum_vacuum_scale_factor"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_scale_factor", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_scale_factor parameter."]}}, "content_hash": "87bdfdad03fbc23fccbd6247f1a37bb7c05736c2fa70d57fead556e6706127f5", "imported_at": "2026-09-27T09:57:59.017", "url": "/wiki/relopts/toast-autovacuum-vacuum-scale-factor/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-scale-factor/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-scale-factor/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-scale-factor/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-scale-factor/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-scale-factor/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-scale-factor/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-scale-factor/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-scale-factor/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-scale-factor/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-scale-factor/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-scale-factor/?v=20"}], "present": true}, {"slug": "toast-autovacuum-vacuum-threshold", "name": "toast.autovacuum_vacuum_threshold", "name_zh": "TOAST autovacuum_vacuum_threshold", "category": "TOAST tables", "summary": "Per-table value for autovacuum_vacuum_threshold parameter.", "aliases": ["autovacuum_vacuum_threshold"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-threshold/?v=10", "label": "Table option autovacuum_vacuum_threshold"}, {"url": "/docs/guc/autovacuum_vacuum_threshold/?v=10", "label": "Global parameter autovacuum_vacuum_threshold"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_threshold", "sha256": "a8c8d51fd43c0e169a2ce6bcb094c1dbd5f0f6cd6e90cabc86f6542039600355"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of updated or deleted tuples needed to trigger a VACUUM in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_threshold parameter."]}, "11": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-threshold/?v=11", "label": "Table option autovacuum_vacuum_threshold"}, {"url": "/docs/guc/autovacuum_vacuum_threshold/?v=11", "label": "Global parameter autovacuum_vacuum_threshold"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_threshold", "sha256": "a553adbaa0edb4dbdf216a59031edf5974a2791c02e12f3a6f23a0df0cdc59d1"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of updated or deleted tuples needed to trigger a VACUUM in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_threshold parameter."]}, "12": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-threshold/?v=12", "label": "Table option autovacuum_vacuum_threshold"}, {"url": "/docs/guc/autovacuum_vacuum_threshold/?v=12", "label": "Global parameter autovacuum_vacuum_threshold"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_threshold", "sha256": "bb486d78e8d17e633e046674781b62e0cf0f77efbb48cd6fffa5fd6b34ac98e6"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of updated or deleted tuples needed to trigger a VACUUM in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_threshold parameter."]}, "13": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-threshold/?v=13", "label": "Table option autovacuum_vacuum_threshold"}, {"url": "/docs/guc/autovacuum_vacuum_threshold/?v=13", "label": "Global parameter autovacuum_vacuum_threshold"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_threshold", "sha256": "d26d014ad3850d3dbbbc1bce41bc267205baa1523b73e48fdd9e7165b6f6785e"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of updated or deleted tuples needed to trigger a VACUUM in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_threshold parameter."]}, "14": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-threshold/?v=14", "label": "Table option autovacuum_vacuum_threshold"}, {"url": "/docs/guc/autovacuum_vacuum_threshold/?v=14", "label": "Global parameter autovacuum_vacuum_threshold"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_threshold", "sha256": "03e821969b789b688f725579aa8bd52763880e798ca8680d894f2c12861724cf"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of updated or deleted tuples needed to trigger a VACUUM in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_threshold parameter."]}, "15": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-threshold/?v=15", "label": "Table option autovacuum_vacuum_threshold"}, {"url": "/docs/guc/autovacuum_vacuum_threshold/?v=15", "label": "Global parameter autovacuum_vacuum_threshold"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_threshold", "sha256": "993bb5fe87856e4c4cb9aedac41232b5915272a65226f57e7fbf0713be2b13f4"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of updated or deleted tuples needed to trigger a VACUUM in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_threshold parameter."]}, "16": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-threshold/?v=16", "label": "Table option autovacuum_vacuum_threshold"}, {"url": "/docs/guc/autovacuum_vacuum_threshold/?v=16", "label": "Global parameter autovacuum_vacuum_threshold"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_threshold", "sha256": "b16c76b3ffb04e1e6601c44b44e2237f2a97916a52ca9b156a820abdf6545547"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of updated or deleted tuples needed to trigger a VACUUM in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_threshold parameter."]}, "17": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-threshold/?v=17", "label": "Table option autovacuum_vacuum_threshold"}, {"url": "/docs/guc/autovacuum_vacuum_threshold/?v=17", "label": "Global parameter autovacuum_vacuum_threshold"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_threshold", "sha256": "8caf714d72c9f2ed5f0f8d65041109e0ab8845c7c1169c0febef5193bdaef36d"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of updated or deleted tuples needed to trigger a VACUUM in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_threshold parameter."]}, "18": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-threshold/?v=18", "label": "Table option autovacuum_vacuum_threshold"}, {"url": "/docs/guc/autovacuum_vacuum_threshold/?v=18", "label": "Global parameter autovacuum_vacuum_threshold"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-THRESHOLD", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_threshold", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of updated or deleted tuples needed to trigger a VACUUM in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_threshold parameter."]}, "19": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-threshold/?v=19", "label": "Table option autovacuum_vacuum_threshold"}, {"url": "/docs/guc/autovacuum_vacuum_threshold/?v=19", "label": "Global parameter autovacuum_vacuum_threshold"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-THRESHOLD", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_threshold", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of updated or deleted tuples needed to trigger a VACUUM in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_threshold parameter."]}, "20": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-autovacuum-vacuum-threshold/?v=20", "label": "Table option autovacuum_vacuum_threshold"}, {"url": "/docs/guc/autovacuum_vacuum_threshold/?v=20", "label": "Global parameter autovacuum_vacuum_threshold"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-THRESHOLD", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_threshold", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of updated or deleted tuples needed to trigger a VACUUM in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.autovacuum_vacuum_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_threshold parameter."]}}, "content_hash": "b9653a9c32c41620ac3bf7535f0485163ab48d6d4b3ea3bb97b8dfd79ed4097d", "imported_at": "2026-09-27T09:57:59.019", "url": "/wiki/relopts/toast-autovacuum-vacuum-threshold/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-threshold/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-threshold/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-threshold/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-threshold/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-threshold/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-threshold/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-threshold/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-threshold/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-threshold/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-threshold/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/toast-autovacuum-vacuum-threshold/?v=20"}], "present": true}, {"slug": "toast-log-autovacuum-min-duration", "name": "toast.log_autovacuum_min_duration", "name_zh": "TOAST log_autovacuum_min_duration", "category": "TOAST tables", "summary": "Per-table value for log_autovacuum_min_duration parameter.", "aliases": ["log_autovacuum_min_duration"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-log-autovacuum-min-duration/?v=10", "label": "Table option log_autovacuum_min_duration"}, {"url": "/docs/guc/log_autovacuum_min_duration/?v=10", "label": "Global parameter log_autovacuum_min_duration"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/runtime-config-autovacuum.html#GUC-LOG-AUTOVACUUM-MIN-DURATION", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: log_autovacuum_min_duration", "sha256": "a8c8d51fd43c0e169a2ce6bcb094c1dbd5f0f6cd6e90cabc86f6542039600355"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: log_autovacuum_min_duration", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Causes each action executed by autovacuum to be logged if it ran for at least the specified number of milliseconds. Setting this to zero logs all autovacuum actions. Minus-one (the default) disables logging autovacuum actions. For example, if you set this to 250ms then all automatic vacuums and analyzes that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1 , a message will be logged if an autovacuum action is skipped due to the existence of a conflicting lock. Enabling this parameter can be helpful in tracking autovacuum activity. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.log_autovacuum_min_duration = value)", "description": ["Per-table value for log_autovacuum_min_duration parameter."]}, "11": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-log-autovacuum-min-duration/?v=11", "label": "Table option log_autovacuum_min_duration"}, {"url": "/docs/guc/log_autovacuum_min_duration/?v=11", "label": "Global parameter log_autovacuum_min_duration"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/runtime-config-autovacuum.html#GUC-LOG-AUTOVACUUM-MIN-DURATION", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: log_autovacuum_min_duration", "sha256": "a553adbaa0edb4dbdf216a59031edf5974a2791c02e12f3a6f23a0df0cdc59d1"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: log_autovacuum_min_duration", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Causes each action executed by autovacuum to be logged if it ran for at least the specified number of milliseconds. Setting this to zero logs all autovacuum actions. Minus-one (the default) disables logging autovacuum actions. For example, if you set this to 250ms then all automatic vacuums and analyzes that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1 , a message will be logged if an autovacuum action is skipped due to a conflicting lock or a concurrently dropped relation. Enabling this parameter can be helpful in tracking autovacuum activity. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.log_autovacuum_min_duration = value)", "description": ["Per-table value for log_autovacuum_min_duration parameter."]}, "12": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-log-autovacuum-min-duration/?v=12", "label": "Table option log_autovacuum_min_duration"}, {"url": "/docs/guc/log_autovacuum_min_duration/?v=12", "label": "Global parameter log_autovacuum_min_duration"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-LOG-AUTOVACUUM-MIN-DURATION", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/runtime-config-autovacuum.html#GUC-LOG-AUTOVACUUM-MIN-DURATION", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: log_autovacuum_min_duration", "sha256": "bb486d78e8d17e633e046674781b62e0cf0f77efbb48cd6fffa5fd6b34ac98e6"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: log_autovacuum_min_duration", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Causes each action executed by autovacuum to be logged if it ran for at least the specified amount of time. Setting this to zero logs all autovacuum actions. -1 (the default) disables logging autovacuum actions. If this value is specified without units, it is taken as milliseconds. For example, if you set this to 250ms then all automatic vacuums and analyzes that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1 , a message will be logged if an autovacuum action is skipped due to a conflicting lock or a concurrently dropped relation. Enabling this parameter can be helpful in tracking autovacuum activity. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.log_autovacuum_min_duration = value)", "description": ["Per-table value for log_autovacuum_min_duration parameter."]}, "13": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-log-autovacuum-min-duration/?v=13", "label": "Table option log_autovacuum_min_duration"}, {"url": "/docs/guc/log_autovacuum_min_duration/?v=13", "label": "Global parameter log_autovacuum_min_duration"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-LOG-AUTOVACUUM-MIN-DURATION", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-autovacuum.html#GUC-LOG-AUTOVACUUM-MIN-DURATION", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: log_autovacuum_min_duration", "sha256": "d26d014ad3850d3dbbbc1bce41bc267205baa1523b73e48fdd9e7165b6f6785e"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: log_autovacuum_min_duration", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Causes each action executed by autovacuum to be logged if it ran for at least the specified amount of time. Setting this to zero logs all autovacuum actions. -1 (the default) disables logging autovacuum actions. If this value is specified without units, it is taken as milliseconds. For example, if you set this to 250ms then all automatic vacuums and analyzes that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1 , a message will be logged if an autovacuum action is skipped due to a conflicting lock or a concurrently dropped relation. Enabling this parameter can be helpful in tracking autovacuum activity. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.log_autovacuum_min_duration = value)", "description": ["Per-table value for log_autovacuum_min_duration parameter."]}, "14": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-log-autovacuum-min-duration/?v=14", "label": "Table option log_autovacuum_min_duration"}, {"url": "/docs/guc/log_autovacuum_min_duration/?v=14", "label": "Global parameter log_autovacuum_min_duration"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-LOG-AUTOVACUUM-MIN-DURATION", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-logging.html#GUC-LOG-AUTOVACUUM-MIN-DURATION", "path": "runtime-config-logging.html", "label": "Related global parameter: log_autovacuum_min_duration", "sha256": "d34de91c4a58cce28aa78480bd98391b5ccad1a35490835101d8d786cd119c29"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: log_autovacuum_min_duration", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Causes each action executed by autovacuum to be logged if it ran for at least the specified amount of time. Setting this to zero logs all autovacuum actions. -1 (the default) disables logging autovacuum actions. If this value is specified without units, it is taken as milliseconds. For example, if you set this to 250ms then all automatic vacuums and analyzes that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1 , a message will be logged if an autovacuum action is skipped due to a conflicting lock or a concurrently dropped relation. Enabling this parameter can be helpful in tracking autovacuum activity. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.log_autovacuum_min_duration = value)", "description": ["Per-table value for log_autovacuum_min_duration parameter."]}, "15": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-log-autovacuum-min-duration/?v=15", "label": "Table option log_autovacuum_min_duration"}, {"url": "/docs/guc/log_autovacuum_min_duration/?v=15", "label": "Global parameter log_autovacuum_min_duration"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-LOG-AUTOVACUUM-MIN-DURATION", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-logging.html#GUC-LOG-AUTOVACUUM-MIN-DURATION", "path": "runtime-config-logging.html", "label": "Related global parameter: log_autovacuum_min_duration", "sha256": "7ba3faabd0ae6bd7f5709873c4a59ff9573e69b3373f0dfe1758409cd64580f0"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: log_autovacuum_min_duration", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Causes each action executed by autovacuum to be logged if it ran for at least the specified amount of time. Setting this to zero logs all autovacuum actions. -1 disables logging autovacuum actions. If this value is specified without units, it is taken as milliseconds. For example, if you set this to 250ms then all automatic vacuums and analyzes that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1 , a message will be logged if an autovacuum action is skipped due to a conflicting lock or a concurrently dropped relation. The default is 10min . Enabling this parameter can be helpful in tracking autovacuum activity. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.log_autovacuum_min_duration = value)", "description": ["Per-table value for log_autovacuum_min_duration parameter."]}, "16": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-log-autovacuum-min-duration/?v=16", "label": "Table option log_autovacuum_min_duration"}, {"url": "/docs/guc/log_autovacuum_min_duration/?v=16", "label": "Global parameter log_autovacuum_min_duration"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-LOG-AUTOVACUUM-MIN-DURATION", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-logging.html#GUC-LOG-AUTOVACUUM-MIN-DURATION", "path": "runtime-config-logging.html", "label": "Related global parameter: log_autovacuum_min_duration", "sha256": "c8d8d9cc2d0adb4e157c6e9e073812844670d9c114ee25527f8266e010f691ec"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: log_autovacuum_min_duration", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Causes each action executed by autovacuum to be logged if it ran for at least the specified amount of time. Setting this to zero logs all autovacuum actions. -1 disables logging autovacuum actions. If this value is specified without units, it is taken as milliseconds. For example, if you set this to 250ms then all automatic vacuums and analyzes that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1 , a message will be logged if an autovacuum action is skipped due to a conflicting lock or a concurrently dropped relation. The default is 10min . Enabling this parameter can be helpful in tracking autovacuum activity. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.log_autovacuum_min_duration = value)", "description": ["Per-table value for log_autovacuum_min_duration parameter."]}, "17": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-log-autovacuum-min-duration/?v=17", "label": "Table option log_autovacuum_min_duration"}, {"url": "/docs/guc/log_autovacuum_min_duration/?v=17", "label": "Global parameter log_autovacuum_min_duration"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-LOG-AUTOVACUUM-MIN-DURATION", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-logging.html#GUC-LOG-AUTOVACUUM-MIN-DURATION", "path": "runtime-config-logging.html", "label": "Related global parameter: log_autovacuum_min_duration", "sha256": "a1791a4a78e8d1860821e85ed3b02fc93d9499434b36a19c03e50edca89759fe"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: log_autovacuum_min_duration", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Causes each action executed by autovacuum to be logged if it ran for at least the specified amount of time. Setting this to zero logs all autovacuum actions. -1 disables logging autovacuum actions. If this value is specified without units, it is taken as milliseconds. For example, if you set this to 250ms then all automatic vacuums and analyzes that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1 , a message will be logged if an autovacuum action is skipped due to a conflicting lock or a concurrently dropped relation. The default is 10min . Enabling this parameter can be helpful in tracking autovacuum activity. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.log_autovacuum_min_duration = value)", "description": ["Per-table value for log_autovacuum_min_duration parameter."]}, "18": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-log-autovacuum-min-duration/?v=18", "label": "Table option log_autovacuum_min_duration"}, {"url": "/docs/guc/log_autovacuum_min_duration/?v=18", "label": "Global parameter log_autovacuum_min_duration"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-LOG-AUTOVACUUM-MIN-DURATION", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-logging.html#GUC-LOG-AUTOVACUUM-MIN-DURATION", "path": "runtime-config-logging.html", "label": "Related global parameter: log_autovacuum_min_duration", "sha256": "93c48c522a72fca19705c4c91a71e951eae653662008eee2e4a9a74a11127fde"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: log_autovacuum_min_duration", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Causes each action executed by autovacuum to be logged if it ran for at least the specified amount of time. Setting this to zero logs all autovacuum actions. -1 disables logging autovacuum actions. If this value is specified without units, it is taken as milliseconds. For example, if you set this to 250ms then all automatic vacuums and analyzes that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1 , a message will be logged if an autovacuum action is skipped due to a conflicting lock or a concurrently dropped relation. The default is 10min . Enabling this parameter can be helpful in tracking autovacuum activity. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.log_autovacuum_min_duration = value)", "description": ["Per-table value for log_autovacuum_min_duration parameter."]}, "19": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-log-autovacuum-min-duration/?v=19", "label": "Table option log_autovacuum_min_duration"}, {"url": "/docs/guc/log_autovacuum_min_duration/?v=19", "label": "Global parameter log_autovacuum_min_duration"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-LOG-AUTOVACUUM-MIN-DURATION", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-logging.html#GUC-LOG-AUTOVACUUM-MIN-DURATION", "path": "runtime-config-logging.html", "label": "Related global parameter: log_autovacuum_min_duration", "sha256": "6bc8c26ccff0749f936162b21d68912f6be287148245e296d602589f7782a116"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: log_autovacuum_min_duration", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Causes vacuum action executed by autovacuum to be logged if it ran for at least the specified amount of time. Setting this to zero logs all vacuum actions by autovacuum. -1 disables logging vacuum actions by autovacuum. If this value is specified without units, it is taken as milliseconds. For example, if you set this to 250ms then all automatic vacuums that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1 , a message will be logged if a vacuum action by autovacuum is skipped due to a conflicting lock or a concurrently dropped relation. The default is 10min . Enabling this parameter can be helpful in tracking vacuum activity by autovacuum. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.log_autovacuum_min_duration = value)", "description": ["Per-table value for log_autovacuum_min_duration parameter."]}, "20": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/relopts/table-log-autovacuum-min-duration/?v=20", "label": "Table option log_autovacuum_min_duration"}, {"url": "/docs/guc/log_autovacuum_min_duration/?v=20", "label": "Global parameter log_autovacuum_min_duration"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-LOG-AUTOVACUUM-MIN-DURATION", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-logging.html#GUC-LOG-AUTOVACUUM-MIN-DURATION", "path": "runtime-config-logging.html", "label": "Related global parameter: log_autovacuum_min_duration", "sha256": "e50a8a5efff74a4907d31c32dc399e8e9974a0df3a1eb2e021afd34f56ed0918"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: log_autovacuum_min_duration", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Causes vacuum action executed by autovacuum to be logged if it ran for at least the specified amount of time. Setting this to zero logs all vacuum actions by autovacuum. -1 disables logging vacuum actions by autovacuum. If this value is specified without units, it is taken as milliseconds. For example, if you set this to 250ms then all automatic vacuums that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1 , a message will be logged if a vacuum action by autovacuum is skipped due to a conflicting lock or a concurrently dropped relation. The default is 10min . Enabling this parameter can be helpful in tracking vacuum activity by autovacuum. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.log_autovacuum_min_duration = value)", "description": ["Per-table value for log_autovacuum_min_duration parameter."]}}, "content_hash": "3aa48f77c77316cae278963e948de3ebc2cca8c5b8a07af61f922b66d43ad28e", "imported_at": "2026-09-27T09:57:59.022", "url": "/wiki/relopts/toast-log-autovacuum-min-duration/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-log-autovacuum-min-duration/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/toast-log-autovacuum-min-duration/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/toast-log-autovacuum-min-duration/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-log-autovacuum-min-duration/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/toast-log-autovacuum-min-duration/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/toast-log-autovacuum-min-duration/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/toast-log-autovacuum-min-duration/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/toast-log-autovacuum-min-duration/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/toast-log-autovacuum-min-duration/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/toast-log-autovacuum-min-duration/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/toast-log-autovacuum-min-duration/?v=20"}], "present": true}, {"slug": "toast-vacuum-index-cleanup", "name": "toast.vacuum_index_cleanup", "name_zh": "TOAST vacuum_index_cleanup", "category": "TOAST tables", "summary": "Forces or disables index cleanup when VACUUM is run on this table. The default value is AUTO . With OFF , index cleanup is disabled, with ON it is enabled, and with AUTO a decision is made dynamically, each time VACUUM runs. The dynamic behavior allows VACUUM to avoid needlessly scanning indexes to remove very few dead tuples. Forcibly disabling all index cleanup can speed up VACUUM very significantly, but may also lead to severely bloated indexes if table modifications are frequent. The INDEX_CLEANUP parameter of VACUUM , if specified, overrides the value of this option.", "aliases": ["vacuum_index_cleanup"], "versions": {"12": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/relopts/table-vacuum-index-cleanup/?v=12", "label": "Table option vacuum_index_cleanup"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-VACUUM-INDEX-CLEANUP", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast.vacuum_index_cleanup = value)", "description": ["Enables or disables index cleanup when VACUUM is run on this table. The default value is true . Disabling index cleanup can speed up VACUUM very significantly, but may also lead to severely bloated indexes if table modifications are frequent. The INDEX_CLEANUP parameter of VACUUM , if specified, overrides the value of this option."]}, "13": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/relopts/table-vacuum-index-cleanup/?v=13", "label": "Table option vacuum_index_cleanup"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-VACUUM-INDEX-CLEANUP", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast.vacuum_index_cleanup = value)", "description": ["Enables or disables index cleanup when VACUUM is run on this table. The default value is true . Disabling index cleanup can speed up VACUUM very significantly, but may also lead to severely bloated indexes if table modifications are frequent. The INDEX_CLEANUP parameter of VACUUM , if specified, overrides the value of this option."]}, "14": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "enum"}], "related": [{"url": "/docs/relopts/table-vacuum-index-cleanup/?v=14", "label": "Table option vacuum_index_cleanup"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-VACUUM-INDEX-CLEANUP", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast.vacuum_index_cleanup = value)", "description": ["Forces or disables index cleanup when VACUUM is run on this table. The default value is AUTO . With OFF , index cleanup is disabled, with ON it is enabled, and with AUTO a decision is made dynamically, each time VACUUM runs. The dynamic behavior allows VACUUM to avoid needlessly scanning indexes to remove very few dead tuples. Forcibly disabling all index cleanup can speed up VACUUM very significantly, but may also lead to severely bloated indexes if table modifications are frequent. The INDEX_CLEANUP parameter of VACUUM , if specified, overrides the value of this option."]}, "15": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "enum"}], "related": [{"url": "/docs/relopts/table-vacuum-index-cleanup/?v=15", "label": "Table option vacuum_index_cleanup"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-VACUUM-INDEX-CLEANUP", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast.vacuum_index_cleanup = value)", "description": ["Forces or disables index cleanup when VACUUM is run on this table. The default value is AUTO . With OFF , index cleanup is disabled, with ON it is enabled, and with AUTO a decision is made dynamically, each time VACUUM runs. The dynamic behavior allows VACUUM to avoid needlessly scanning indexes to remove very few dead tuples. Forcibly disabling all index cleanup can speed up VACUUM very significantly, but may also lead to severely bloated indexes if table modifications are frequent. The INDEX_CLEANUP parameter of VACUUM , if specified, overrides the value of this option."]}, "16": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "enum"}], "related": [{"url": "/docs/relopts/table-vacuum-index-cleanup/?v=16", "label": "Table option vacuum_index_cleanup"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-VACUUM-INDEX-CLEANUP", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast.vacuum_index_cleanup = value)", "description": ["Forces or disables index cleanup when VACUUM is run on this table. The default value is AUTO . With OFF , index cleanup is disabled, with ON it is enabled, and with AUTO a decision is made dynamically, each time VACUUM runs. The dynamic behavior allows VACUUM to avoid needlessly scanning indexes to remove very few dead tuples. Forcibly disabling all index cleanup can speed up VACUUM very significantly, but may also lead to severely bloated indexes if table modifications are frequent. The INDEX_CLEANUP parameter of VACUUM , if specified, overrides the value of this option."]}, "17": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "enum"}], "related": [{"url": "/docs/relopts/table-vacuum-index-cleanup/?v=17", "label": "Table option vacuum_index_cleanup"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-VACUUM-INDEX-CLEANUP", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast.vacuum_index_cleanup = value)", "description": ["Forces or disables index cleanup when VACUUM is run on this table. The default value is AUTO . With OFF , index cleanup is disabled, with ON it is enabled, and with AUTO a decision is made dynamically, each time VACUUM runs. The dynamic behavior allows VACUUM to avoid needlessly scanning indexes to remove very few dead tuples. Forcibly disabling all index cleanup can speed up VACUUM very significantly, but may also lead to severely bloated indexes if table modifications are frequent. The INDEX_CLEANUP parameter of VACUUM , if specified, overrides the value of this option."]}, "18": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "enum"}], "related": [{"url": "/docs/relopts/table-vacuum-index-cleanup/?v=18", "label": "Table option vacuum_index_cleanup"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-VACUUM-INDEX-CLEANUP", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast.vacuum_index_cleanup = value)", "description": ["Forces or disables index cleanup when VACUUM is run on this table. The default value is AUTO . With OFF , index cleanup is disabled, with ON it is enabled, and with AUTO a decision is made dynamically, each time VACUUM runs. The dynamic behavior allows VACUUM to avoid needlessly scanning indexes to remove very few dead tuples. Forcibly disabling all index cleanup can speed up VACUUM very significantly, but may also lead to severely bloated indexes if table modifications are frequent. The INDEX_CLEANUP parameter of VACUUM , if specified, overrides the value of this option."]}, "19": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "enum"}], "related": [{"url": "/docs/relopts/table-vacuum-index-cleanup/?v=19", "label": "Table option vacuum_index_cleanup"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-VACUUM-INDEX-CLEANUP", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast.vacuum_index_cleanup = value)", "description": ["Forces or disables index cleanup when VACUUM is run on this table. The default value is AUTO . With OFF , index cleanup is disabled, with ON it is enabled, and with AUTO a decision is made dynamically, each time VACUUM runs. The dynamic behavior allows VACUUM to avoid needlessly scanning indexes to remove very few dead tuples. Forcibly disabling all index cleanup can speed up VACUUM very significantly, but may also lead to severely bloated indexes if table modifications are frequent. The INDEX_CLEANUP parameter of VACUUM , if specified, overrides the value of this option."]}, "20": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "enum"}], "related": [{"url": "/docs/relopts/table-vacuum-index-cleanup/?v=20", "label": "Table option vacuum_index_cleanup"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-VACUUM-INDEX-CLEANUP", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast.vacuum_index_cleanup = value)", "description": ["Forces or disables index cleanup when VACUUM is run on this table. The default value is AUTO . With OFF , index cleanup is disabled, with ON it is enabled, and with AUTO a decision is made dynamically, each time VACUUM runs. The dynamic behavior allows VACUUM to avoid needlessly scanning indexes to remove very few dead tuples. Forcibly disabling all index cleanup can speed up VACUUM very significantly, but may also lead to severely bloated indexes if table modifications are frequent. The INDEX_CLEANUP parameter of VACUUM , if specified, overrides the value of this option."]}}, "content_hash": "4f6191cc9220ad8f9986021635d127100985148e7e9007f1799d57240c335bae", "imported_at": "2026-09-27T09:57:59.025", "url": "/wiki/relopts/toast-vacuum-index-cleanup/?v=18", "cells": [{"major": "10", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 10.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-vacuum-index-cleanup/?v=10"}, {"major": "11", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 11.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-vacuum-index-cleanup/?v=11"}, {"major": "12", "state": "added", "label": "First recorded in this sample", "title": "PostgreSQL 12.22 \u00b7 First recorded in this sample", "url": "/wiki/relopts/toast-vacuum-index-cleanup/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-vacuum-index-cleanup/?v=13"}, {"major": "14", "state": "changed", "label": "Interface or attribute change", "title": "PostgreSQL 14.24 \u00b7 Interface or attribute change", "url": "/wiki/relopts/toast-vacuum-index-cleanup/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/toast-vacuum-index-cleanup/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/toast-vacuum-index-cleanup/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/toast-vacuum-index-cleanup/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/toast-vacuum-index-cleanup/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/toast-vacuum-index-cleanup/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/toast-vacuum-index-cleanup/?v=20"}], "present": true}, {"slug": "toast-vacuum-max-eager-freeze-failure-rate", "name": "toast.vacuum_max_eager_freeze_failure_rate", "name_zh": "TOAST vacuum_max_eager_freeze_failure_rate", "category": "TOAST tables", "summary": "Per-table value for vacuum_max_eager_freeze_failure_rate parameter.", "aliases": ["vacuum_max_eager_freeze_failure_rate"], "versions": {"18": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-vacuum-max-eager-freeze-failure-rate/?v=18", "label": "Table option vacuum_max_eager_freeze_failure_rate"}, {"url": "/docs/guc/vacuum_max_eager_freeze_failure_rate/?v=18", "label": "Global parameter vacuum_max_eager_freeze_failure_rate"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-VACUUM-MAX-EAGER-FREEZE-FAILURE-RATE", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-VACUUM-MAX-EAGER-FREEZE-FAILURE-RATE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_max_eager_freeze_failure_rate", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_max_eager_freeze_failure_rate", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum number of pages (as a fraction of total pages in the relation) that VACUUM may scan and fail to set all-frozen in the visibility map before disabling eager scanning. A value of 0 disables eager scanning altogether. The default is 0.03 (3%).", "Note that when eager scanning is enabled, only freeze failures count against the cap, not successful freezing. Successful page freezes are capped internally at 20% of the all-visible but not all-frozen pages in the relation. Capping successful page freezes helps amortize the overhead across multiple normal vacuums and limits the potential downside of wasted eager freezes of pages that are modified again before the next aggressive vacuum.", "This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing the corresponding table storage parameter . For more information on tuning vacuum's freezing behavior, see Section 24.1.5 ."]}], "signature": "WITH (toast.vacuum_max_eager_freeze_failure_rate = value)", "description": ["Per-table value for vacuum_max_eager_freeze_failure_rate parameter."]}, "19": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-vacuum-max-eager-freeze-failure-rate/?v=19", "label": "Table option vacuum_max_eager_freeze_failure_rate"}, {"url": "/docs/guc/vacuum_max_eager_freeze_failure_rate/?v=19", "label": "Global parameter vacuum_max_eager_freeze_failure_rate"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-VACUUM-MAX-EAGER-FREEZE-FAILURE-RATE", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-VACUUM-MAX-EAGER-FREEZE-FAILURE-RATE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_max_eager_freeze_failure_rate", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_max_eager_freeze_failure_rate", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum number of pages (as a fraction of total pages in the relation) that VACUUM may scan and fail to set all-frozen in the visibility map before disabling eager scanning. A value of 0 disables eager scanning altogether. The default is 0.03 (3%).", "Note that when eager scanning is enabled, only freeze failures count against the cap, not successful freezing. Successful page freezes are capped internally at 20% of the all-visible but not all-frozen pages in the relation. Capping successful page freezes helps amortize the overhead across multiple normal vacuums and limits the potential downside of wasted eager freezes of pages that are modified again before the next aggressive vacuum.", "This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing the corresponding table storage parameter . For more information on tuning vacuum's freezing behavior, see Section 24.1.5 ."]}], "signature": "WITH (toast.vacuum_max_eager_freeze_failure_rate = value)", "description": ["Per-table value for vacuum_max_eager_freeze_failure_rate parameter."]}, "20": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/relopts/table-vacuum-max-eager-freeze-failure-rate/?v=20", "label": "Table option vacuum_max_eager_freeze_failure_rate"}, {"url": "/docs/guc/vacuum_max_eager_freeze_failure_rate/?v=20", "label": "Global parameter vacuum_max_eager_freeze_failure_rate"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-VACUUM-MAX-EAGER-FREEZE-FAILURE-RATE", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-VACUUM-MAX-EAGER-FREEZE-FAILURE-RATE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_max_eager_freeze_failure_rate", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_max_eager_freeze_failure_rate", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum number of pages (as a fraction of total pages in the relation) that VACUUM may scan and fail to set all-frozen in the visibility map before disabling eager scanning. A value of 0 disables eager scanning altogether. The default is 0.03 (3%).", "Note that when eager scanning is enabled, only freeze failures count against the cap, not successful freezing. Successful page freezes are capped internally at 20% of the all-visible but not all-frozen pages in the relation. Capping successful page freezes helps amortize the overhead across multiple normal vacuums and limits the potential downside of wasted eager freezes of pages that are modified again before the next aggressive vacuum.", "This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing the corresponding table storage parameter . For more information on tuning vacuum's freezing behavior, see Section 24.1.5 ."]}], "signature": "WITH (toast.vacuum_max_eager_freeze_failure_rate = value)", "description": ["Per-table value for vacuum_max_eager_freeze_failure_rate parameter."]}}, "content_hash": "e187a0592ed5e4a84ea1f833a6da7804470ec47937b397f22cec3f59d385ee65", "imported_at": "2026-09-27T09:57:59.028", "url": "/wiki/relopts/toast-vacuum-max-eager-freeze-failure-rate/?v=18", "cells": [{"major": "10", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 10.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-vacuum-max-eager-freeze-failure-rate/?v=10"}, {"major": "11", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 11.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-vacuum-max-eager-freeze-failure-rate/?v=11"}, {"major": "12", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 12.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-vacuum-max-eager-freeze-failure-rate/?v=12"}, {"major": "13", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 13.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-vacuum-max-eager-freeze-failure-rate/?v=13"}, {"major": "14", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 14.24 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-vacuum-max-eager-freeze-failure-rate/?v=14"}, {"major": "15", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 15.19 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-vacuum-max-eager-freeze-failure-rate/?v=15"}, {"major": "16", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 16.15 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-vacuum-max-eager-freeze-failure-rate/?v=16"}, {"major": "17", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 17.11 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-vacuum-max-eager-freeze-failure-rate/?v=17"}, {"major": "18", "state": "added", "label": "First recorded in this sample", "title": "PostgreSQL 18.6 \u00b7 First recorded in this sample", "url": "/wiki/relopts/toast-vacuum-max-eager-freeze-failure-rate/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/toast-vacuum-max-eager-freeze-failure-rate/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/toast-vacuum-max-eager-freeze-failure-rate/?v=20"}], "present": true}, {"slug": "toast-vacuum-truncate", "name": "toast.vacuum_truncate", "name_zh": "TOAST vacuum_truncate", "category": "TOAST tables", "summary": "Per-table value for vacuum_truncate parameter. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this option.", "aliases": ["vacuum_truncate"], "versions": {"12": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/relopts/table-vacuum-truncate/?v=12", "label": "Table option vacuum_truncate"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-VACUUM-TRUNCATE", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast.vacuum_truncate = value)", "description": ["Enables or disables vacuum to try to truncate off any empty pages at the end of this table. The default value is true . If true , VACUUM and autovacuum do the truncation and the disk space for the truncated pages is returned to the operating system. Note that the truncation requires ACCESS EXCLUSIVE lock on the table. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this option."]}, "13": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/relopts/table-vacuum-truncate/?v=13", "label": "Table option vacuum_truncate"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-VACUUM-TRUNCATE", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast.vacuum_truncate = value)", "description": ["Enables or disables vacuum to try to truncate off any empty pages at the end of this table. The default value is true . If true , VACUUM and autovacuum do the truncation and the disk space for the truncated pages is returned to the operating system. Note that the truncation requires ACCESS EXCLUSIVE lock on the table. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this option."]}, "14": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/relopts/table-vacuum-truncate/?v=14", "label": "Table option vacuum_truncate"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-VACUUM-TRUNCATE", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast.vacuum_truncate = value)", "description": ["Enables or disables vacuum to try to truncate off any empty pages at the end of this table. The default value is true . If true , VACUUM and autovacuum do the truncation and the disk space for the truncated pages is returned to the operating system. Note that the truncation requires ACCESS EXCLUSIVE lock on the table. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this option."]}, "15": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/relopts/table-vacuum-truncate/?v=15", "label": "Table option vacuum_truncate"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-VACUUM-TRUNCATE", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast.vacuum_truncate = value)", "description": ["Enables or disables vacuum to try to truncate off any empty pages at the end of this table. The default value is true . If true , VACUUM and autovacuum do the truncation and the disk space for the truncated pages is returned to the operating system. Note that the truncation requires ACCESS EXCLUSIVE lock on the table. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this option."]}, "16": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/relopts/table-vacuum-truncate/?v=16", "label": "Table option vacuum_truncate"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-VACUUM-TRUNCATE", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast.vacuum_truncate = value)", "description": ["Enables or disables vacuum to try to truncate off any empty pages at the end of this table. The default value is true . If true , VACUUM and autovacuum do the truncation and the disk space for the truncated pages is returned to the operating system. Note that the truncation requires ACCESS EXCLUSIVE lock on the table. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this option."]}, "17": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/relopts/table-vacuum-truncate/?v=17", "label": "Table option vacuum_truncate"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-VACUUM-TRUNCATE", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast.vacuum_truncate = value)", "description": ["Enables or disables vacuum to try to truncate off any empty pages at the end of this table. The default value is true . If true , VACUUM and autovacuum do the truncation and the disk space for the truncated pages is returned to the operating system. Note that the truncation requires ACCESS EXCLUSIVE lock on the table. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this option."]}, "18": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/relopts/table-vacuum-truncate/?v=18", "label": "Table option vacuum_truncate"}, {"url": "/docs/guc/vacuum_truncate/?v=18", "label": "Global parameter vacuum_truncate"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-VACUUM-TRUNCATE", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-VACUUM-TRUNCATE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_truncate", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_truncate", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Enables or disables vacuum to try to truncate off any empty pages at the end of the table. The default value is true . If true , VACUUM and autovacuum do the truncation and the disk space for the truncated pages is returned to the operating system. Note that the truncation requires an ACCESS EXCLUSIVE lock on the table. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this parameter. The setting can also be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.vacuum_truncate = value)", "description": ["Per-table value for vacuum_truncate parameter. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this option."]}, "19": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/relopts/table-vacuum-truncate/?v=19", "label": "Table option vacuum_truncate"}, {"url": "/docs/guc/vacuum_truncate/?v=19", "label": "Global parameter vacuum_truncate"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-VACUUM-TRUNCATE", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-VACUUM-TRUNCATE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_truncate", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_truncate", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Enables or disables vacuum to try to truncate off any empty pages at the end of the table. The default value is true . If true , VACUUM and autovacuum do the truncation and the disk space for the truncated pages is returned to the operating system. Note that the truncation requires an ACCESS EXCLUSIVE lock on the table. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this parameter. The setting can also be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.vacuum_truncate = value)", "description": ["Per-table value for vacuum_truncate parameter. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this option."]}, "20": {"facts": [{"label": "Applies to", "value": "TOAST tables"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/relopts/table-vacuum-truncate/?v=20", "label": "Table option vacuum_truncate"}, {"url": "/docs/guc/vacuum_truncate/?v=20", "label": "Global parameter vacuum_truncate"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-VACUUM-TRUNCATE", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-VACUUM-TRUNCATE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_truncate", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "TOAST inheritance", "paragraphs": ["This option applies to the associated TOAST table. Set it with the toast. prefix in WITH or ALTER TABLE SET. An unset TOAST option inherits the corresponding explicitly set parent-table option.", "The manual describes table and TOAST forms together. Autoanalyze does not apply to TOAST tables; only explicitly documented toast. forms are listed here."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_truncate", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Enables or disables vacuum to try to truncate off any empty pages at the end of the table. The default value is true . If true , VACUUM and autovacuum do the truncation and the disk space for the truncated pages is returned to the operating system. Note that the truncation requires an ACCESS EXCLUSIVE lock on the table. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this parameter. The setting can also be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (toast.vacuum_truncate = value)", "description": ["Per-table value for vacuum_truncate parameter. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this option."]}}, "content_hash": "676295d0eaa425fcbf18c4cb601d6a2bcf0b5ca8fe6278bdd43ce93ad2b44e2a", "imported_at": "2026-09-27T09:57:59.031", "url": "/wiki/relopts/toast-vacuum-truncate/?v=18", "cells": [{"major": "10", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 10.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-vacuum-truncate/?v=10"}, {"major": "11", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 11.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/toast-vacuum-truncate/?v=11"}, {"major": "12", "state": "added", "label": "First recorded in this sample", "title": "PostgreSQL 12.22 \u00b7 First recorded in this sample", "url": "/wiki/relopts/toast-vacuum-truncate/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/toast-vacuum-truncate/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/toast-vacuum-truncate/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/toast-vacuum-truncate/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/toast-vacuum-truncate/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/toast-vacuum-truncate/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/toast-vacuum-truncate/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/toast-vacuum-truncate/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/toast-vacuum-truncate/?v=20"}], "present": true}, {"slug": "table-oids", "name": "oids", "name_zh": "oids", "category": "Table compatibility options", "summary": "This clause specifies optional storage parameters for a table or index; see Storage Parameters below for more information. For backward-compatibility the WITH clause for a table can also include OIDS=FALSE to specify that rows of the new table should not contain OIDs (object identifiers), OIDS=TRUE is not supported anymore.", "aliases": ["compat.oids"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "Historical table syntax"}, {"label": "Value", "value": "TRUE / FALSE"}], "related": [{"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}], "sections": [{"title": "Compatibility option", "paragraphs": ["This is historical CREATE TABLE row-OID syntax. It is not a physical tuning parameter stored in pg_class.reloptions. Allowed values depend on the selected version."]}], "signature": "WITH (OIDS = TRUE | FALSE)", "description": ["This clause specifies optional storage parameters for a table or index; see Storage Parameters for more information. The WITH clause for a table can also include OIDS=TRUE (or just OIDS ) to specify that rows of the new table should have OIDs (object identifiers) assigned to them, or OIDS=FALSE to specify that the rows should not have OIDs. If OIDS is not specified, the default setting depends upon the default_with_oids configuration parameter. (If the new table inherits from any tables that have OIDs, then OIDS=TRUE is forced even if the command says OIDS=FALSE .)", "If OIDS=FALSE is specified or implied, the new table does not store OIDs and no OID will be assigned for a row inserted into it. This is generally considered worthwhile, since it will reduce OID consumption and thereby postpone the wraparound of the 32-bit OID counter. Once the counter wraps around, OIDs can no longer be assumed to be unique, which makes them considerably less useful. In addition, excluding OIDs from a table reduces the space required to store the table on disk by 4 bytes per row (on most machines), slightly improving performance.", "To remove OIDs from a table after it has been created, use ALTER TABLE ."]}, "11": {"facts": [{"label": "Applies to", "value": "Historical table syntax"}, {"label": "Value", "value": "TRUE / FALSE"}], "related": [{"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}], "sections": [{"title": "Compatibility option", "paragraphs": ["This is historical CREATE TABLE row-OID syntax. It is not a physical tuning parameter stored in pg_class.reloptions. Allowed values depend on the selected version."]}], "signature": "WITH (OIDS = TRUE | FALSE)", "description": ["This clause specifies optional storage parameters for a table or index; see Storage Parameters for more information. The WITH clause for a table can also include OIDS=TRUE (or just OIDS ) to specify that rows of the new table should have OIDs (object identifiers) assigned to them, or OIDS=FALSE to specify that the rows should not have OIDs. If OIDS is not specified, the default setting depends upon the default_with_oids configuration parameter. (If the new table inherits from any tables that have OIDs, then OIDS=TRUE is forced even if the command says OIDS=FALSE .)", "If OIDS=FALSE is specified or implied, the new table does not store OIDs and no OID will be assigned for a row inserted into it. This is generally considered worthwhile, since it will reduce OID consumption and thereby postpone the wraparound of the 32-bit OID counter. Once the counter wraps around, OIDs can no longer be assumed to be unique, which makes them considerably less useful. In addition, excluding OIDs from a table reduces the space required to store the table on disk by 4 bytes per row (on most machines), slightly improving performance.", "To remove OIDs from a table after it has been created, use ALTER TABLE ."]}, "12": {"facts": [{"label": "Applies to", "value": "Historical table syntax"}, {"label": "Value", "value": "FALSE only"}], "related": [{"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}], "sections": [{"title": "Compatibility option", "paragraphs": ["This is historical CREATE TABLE row-OID syntax. It is not a physical tuning parameter stored in pg_class.reloptions. Allowed values depend on the selected version."]}], "signature": "WITH (OIDS = FALSE)", "description": ["This clause specifies optional storage parameters for a table or index; see Storage Parameters for more information. For backward-compatibility the WITH clause for a table can also include OIDS=FALSE to specify that rows of the new table should not contain OIDs (object identifiers), OIDS=TRUE is not supported anymore."]}, "13": {"facts": [{"label": "Applies to", "value": "Historical table syntax"}, {"label": "Value", "value": "FALSE only"}], "related": [{"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}], "sections": [{"title": "Compatibility option", "paragraphs": ["This is historical CREATE TABLE row-OID syntax. It is not a physical tuning parameter stored in pg_class.reloptions. Allowed values depend on the selected version."]}], "signature": "WITH (OIDS = FALSE)", "description": ["This clause specifies optional storage parameters for a table or index; see Storage Parameters below for more information. For backward-compatibility the WITH clause for a table can also include OIDS=FALSE to specify that rows of the new table should not contain OIDs (object identifiers), OIDS=TRUE is not supported anymore."]}, "14": {"facts": [{"label": "Applies to", "value": "Historical table syntax"}, {"label": "Value", "value": "FALSE only"}], "related": [{"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}], "sections": [{"title": "Compatibility option", "paragraphs": ["This is historical CREATE TABLE row-OID syntax. It is not a physical tuning parameter stored in pg_class.reloptions. Allowed values depend on the selected version."]}], "signature": "WITH (OIDS = FALSE)", "description": ["This clause specifies optional storage parameters for a table or index; see Storage Parameters below for more information. For backward-compatibility the WITH clause for a table can also include OIDS=FALSE to specify that rows of the new table should not contain OIDs (object identifiers), OIDS=TRUE is not supported anymore."]}, "15": {"facts": [{"label": "Applies to", "value": "Historical table syntax"}, {"label": "Value", "value": "FALSE only"}], "related": [{"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}], "sections": [{"title": "Compatibility option", "paragraphs": ["This is historical CREATE TABLE row-OID syntax. It is not a physical tuning parameter stored in pg_class.reloptions. Allowed values depend on the selected version."]}], "signature": "WITH (OIDS = FALSE)", "description": ["This clause specifies optional storage parameters for a table or index; see Storage Parameters below for more information. For backward-compatibility the WITH clause for a table can also include OIDS=FALSE to specify that rows of the new table should not contain OIDs (object identifiers), OIDS=TRUE is not supported anymore."]}, "16": {"facts": [{"label": "Applies to", "value": "Historical table syntax"}, {"label": "Value", "value": "FALSE only"}], "related": [{"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#SQL-CREATETABLE-PARMS-WITH", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}], "sections": [{"title": "Compatibility option", "paragraphs": ["This is historical CREATE TABLE row-OID syntax. It is not a physical tuning parameter stored in pg_class.reloptions. Allowed values depend on the selected version."]}], "signature": "WITH (OIDS = FALSE)", "description": ["This clause specifies optional storage parameters for a table or index; see Storage Parameters below for more information. For backward-compatibility the WITH clause for a table can also include OIDS=FALSE to specify that rows of the new table should not contain OIDs (object identifiers), OIDS=TRUE is not supported anymore."]}, "17": {"facts": [{"label": "Applies to", "value": "Historical table syntax"}, {"label": "Value", "value": "FALSE only"}], "related": [{"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#SQL-CREATETABLE-PARMS-WITH", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}], "sections": [{"title": "Compatibility option", "paragraphs": ["This is historical CREATE TABLE row-OID syntax. It is not a physical tuning parameter stored in pg_class.reloptions. Allowed values depend on the selected version."]}], "signature": "WITH (OIDS = FALSE)", "description": ["This clause specifies optional storage parameters for a table or index; see Storage Parameters below for more information. For backward-compatibility the WITH clause for a table can also include OIDS=FALSE to specify that rows of the new table should not contain OIDs (object identifiers), OIDS=TRUE is not supported anymore."]}, "18": {"facts": [{"label": "Applies to", "value": "Historical table syntax"}, {"label": "Value", "value": "FALSE only"}], "related": [{"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#SQL-CREATETABLE-PARMS-WITH", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}], "sections": [{"title": "Compatibility option", "paragraphs": ["This is historical CREATE TABLE row-OID syntax. It is not a physical tuning parameter stored in pg_class.reloptions. Allowed values depend on the selected version."]}], "signature": "WITH (OIDS = FALSE)", "description": ["This clause specifies optional storage parameters for a table or index; see Storage Parameters below for more information. For backward-compatibility the WITH clause for a table can also include OIDS=FALSE to specify that rows of the new table should not contain OIDs (object identifiers), OIDS=TRUE is not supported anymore."]}, "19": {"facts": [{"label": "Applies to", "value": "Historical table syntax"}, {"label": "Value", "value": "FALSE only"}], "related": [{"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#SQL-CREATETABLE-PARMS-WITH", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}], "sections": [{"title": "Compatibility option", "paragraphs": ["This is historical CREATE TABLE row-OID syntax. It is not a physical tuning parameter stored in pg_class.reloptions. Allowed values depend on the selected version."]}], "signature": "WITH (OIDS = FALSE)", "description": ["This clause specifies optional storage parameters for a table or index; see Storage Parameters below for more information. For backward-compatibility the WITH clause for a table can also include OIDS=FALSE to specify that rows of the new table should not contain OIDs (object identifiers), OIDS=TRUE is not supported anymore."]}, "20": {"facts": [{"label": "Applies to", "value": "Historical table syntax"}, {"label": "Value", "value": "FALSE only"}], "related": [{"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#SQL-CREATETABLE-PARMS-WITH", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}], "sections": [{"title": "Compatibility option", "paragraphs": ["This is historical CREATE TABLE row-OID syntax. It is not a physical tuning parameter stored in pg_class.reloptions. Allowed values depend on the selected version."]}], "signature": "WITH (OIDS = FALSE)", "description": ["This clause specifies optional storage parameters for a table or index; see Storage Parameters below for more information. For backward-compatibility the WITH clause for a table can also include OIDS=FALSE to specify that rows of the new table should not contain OIDs (object identifiers), OIDS=TRUE is not supported anymore."]}}, "content_hash": "667d82b953fedd024c0bcb44cd9e599825ca5d8410d1fc0a450ec74af0c2748e", "imported_at": "2026-09-27T09:57:58.964", "url": "/wiki/relopts/table-oids/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/table-oids/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/table-oids/?v=11"}, {"major": "12", "state": "changed", "label": "Interface or attribute change", "title": "PostgreSQL 12.22 \u00b7 Interface or attribute change", "url": "/wiki/relopts/table-oids/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/table-oids/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/table-oids/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/table-oids/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/table-oids/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/table-oids/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/table-oids/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-oids/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-oids/?v=20"}], "present": true}, {"slug": "table-autovacuum-analyze-scale-factor", "name": "autovacuum_analyze_scale_factor", "name_zh": "autovacuum_analyze_scale_factor", "category": "Tables and materialized views", "summary": "Per-table value for autovacuum_analyze_scale_factor parameter.", "aliases": ["table.autovacuum_analyze_scale_factor"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_analyze_scale_factor/?v=10", "label": "Global parameter autovacuum_analyze_scale_factor"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/runtime-config-autovacuum.html#GUC-AUTOVACUUM-ANALYZE-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_analyze_scale_factor", "sha256": "a8c8d51fd43c0e169a2ce6bcb094c1dbd5f0f6cd6e90cabc86f6542039600355"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_analyze_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_analyze_threshold when deciding whether to trigger an ANALYZE . The default is 0.1 (10% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_analyze_scale_factor = value)", "description": ["Per-table value for autovacuum_analyze_scale_factor parameter."]}, "11": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_analyze_scale_factor/?v=11", "label": "Global parameter autovacuum_analyze_scale_factor"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/runtime-config-autovacuum.html#GUC-AUTOVACUUM-ANALYZE-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_analyze_scale_factor", "sha256": "a553adbaa0edb4dbdf216a59031edf5974a2791c02e12f3a6f23a0df0cdc59d1"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_analyze_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_analyze_threshold when deciding whether to trigger an ANALYZE . The default is 0.1 (10% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_analyze_scale_factor = value)", "description": ["Per-table value for autovacuum_analyze_scale_factor parameter."]}, "12": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_analyze_scale_factor/?v=12", "label": "Global parameter autovacuum_analyze_scale_factor"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-AUTOVACUUM-ANALYZE-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/runtime-config-autovacuum.html#GUC-AUTOVACUUM-ANALYZE-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_analyze_scale_factor", "sha256": "bb486d78e8d17e633e046674781b62e0cf0f77efbb48cd6fffa5fd6b34ac98e6"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_analyze_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_analyze_threshold when deciding whether to trigger an ANALYZE . The default is 0.1 (10% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_analyze_scale_factor = value)", "description": ["Per-table value for autovacuum_analyze_scale_factor parameter."]}, "13": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_analyze_scale_factor/?v=13", "label": "Global parameter autovacuum_analyze_scale_factor"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-ANALYZE-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-autovacuum.html#GUC-AUTOVACUUM-ANALYZE-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_analyze_scale_factor", "sha256": "d26d014ad3850d3dbbbc1bce41bc267205baa1523b73e48fdd9e7165b6f6785e"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_analyze_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_analyze_threshold when deciding whether to trigger an ANALYZE . The default is 0.1 (10% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_analyze_scale_factor = value)", "description": ["Per-table value for autovacuum_analyze_scale_factor parameter."]}, "14": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_analyze_scale_factor/?v=14", "label": "Global parameter autovacuum_analyze_scale_factor"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-ANALYZE-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-autovacuum.html#GUC-AUTOVACUUM-ANALYZE-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_analyze_scale_factor", "sha256": "03e821969b789b688f725579aa8bd52763880e798ca8680d894f2c12861724cf"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_analyze_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_analyze_threshold when deciding whether to trigger an ANALYZE . The default is 0.1 (10% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_analyze_scale_factor = value)", "description": ["Per-table value for autovacuum_analyze_scale_factor parameter."]}, "15": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_analyze_scale_factor/?v=15", "label": "Global parameter autovacuum_analyze_scale_factor"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-ANALYZE-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-autovacuum.html#GUC-AUTOVACUUM-ANALYZE-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_analyze_scale_factor", "sha256": "993bb5fe87856e4c4cb9aedac41232b5915272a65226f57e7fbf0713be2b13f4"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_analyze_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_analyze_threshold when deciding whether to trigger an ANALYZE . The default is 0.1 (10% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_analyze_scale_factor = value)", "description": ["Per-table value for autovacuum_analyze_scale_factor parameter."]}, "16": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_analyze_scale_factor/?v=16", "label": "Global parameter autovacuum_analyze_scale_factor"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-ANALYZE-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-autovacuum.html#GUC-AUTOVACUUM-ANALYZE-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_analyze_scale_factor", "sha256": "b16c76b3ffb04e1e6601c44b44e2237f2a97916a52ca9b156a820abdf6545547"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_analyze_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_analyze_threshold when deciding whether to trigger an ANALYZE . The default is 0.1 (10% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_analyze_scale_factor = value)", "description": ["Per-table value for autovacuum_analyze_scale_factor parameter."]}, "17": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_analyze_scale_factor/?v=17", "label": "Global parameter autovacuum_analyze_scale_factor"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-ANALYZE-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-autovacuum.html#GUC-AUTOVACUUM-ANALYZE-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_analyze_scale_factor", "sha256": "8caf714d72c9f2ed5f0f8d65041109e0ab8845c7c1169c0febef5193bdaef36d"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_analyze_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_analyze_threshold when deciding whether to trigger an ANALYZE . The default is 0.1 (10% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_analyze_scale_factor = value)", "description": ["Per-table value for autovacuum_analyze_scale_factor parameter."]}, "18": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_analyze_scale_factor/?v=18", "label": "Global parameter autovacuum_analyze_scale_factor"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-ANALYZE-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-ANALYZE-SCALE-FACTOR", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_analyze_scale_factor", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_analyze_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_analyze_threshold when deciding whether to trigger an ANALYZE . The default is 0.1 (10% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_analyze_scale_factor = value)", "description": ["Per-table value for autovacuum_analyze_scale_factor parameter."]}, "19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_analyze_scale_factor/?v=19", "label": "Global parameter autovacuum_analyze_scale_factor"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-ANALYZE-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-AUTOVACUUM-ANALYZE-SCALE-FACTOR", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_analyze_scale_factor", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_analyze_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_analyze_threshold when deciding whether to trigger an ANALYZE . The default is 0.1 (10% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_analyze_scale_factor = value)", "description": ["Per-table value for autovacuum_analyze_scale_factor parameter."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_analyze_scale_factor/?v=20", "label": "Global parameter autovacuum_analyze_scale_factor"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-ANALYZE-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-AUTOVACUUM-ANALYZE-SCALE-FACTOR", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_analyze_scale_factor", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_analyze_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_analyze_threshold when deciding whether to trigger an ANALYZE . The default is 0.1 (10% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_analyze_scale_factor = value)", "description": ["Per-table value for autovacuum_analyze_scale_factor parameter."]}}, "content_hash": "f94f03feca7e831d2c4449bdf1660cecc164b661985315a3d394a96aea68783a", "imported_at": "2026-09-27T09:57:58.923", "url": "/wiki/relopts/table-autovacuum-analyze-scale-factor/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-analyze-scale-factor/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-analyze-scale-factor/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-analyze-scale-factor/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-analyze-scale-factor/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-analyze-scale-factor/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-analyze-scale-factor/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-analyze-scale-factor/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-analyze-scale-factor/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-analyze-scale-factor/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-analyze-scale-factor/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-analyze-scale-factor/?v=20"}], "present": true}, {"slug": "table-autovacuum-analyze-threshold", "name": "autovacuum_analyze_threshold", "name_zh": "autovacuum_analyze_threshold", "category": "Tables and materialized views", "summary": "Per-table value for autovacuum_analyze_threshold parameter.", "aliases": ["table.autovacuum_analyze_threshold"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_analyze_threshold/?v=10", "label": "Global parameter autovacuum_analyze_threshold"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/runtime-config-autovacuum.html#GUC-AUTOVACUUM-ANALYZE-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_analyze_threshold", "sha256": "a8c8d51fd43c0e169a2ce6bcb094c1dbd5f0f6cd6e90cabc86f6542039600355"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_analyze_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of inserted, updated or deleted tuples needed to trigger an ANALYZE in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_analyze_threshold = value)", "description": ["Per-table value for autovacuum_analyze_threshold parameter."]}, "11": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_analyze_threshold/?v=11", "label": "Global parameter autovacuum_analyze_threshold"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/runtime-config-autovacuum.html#GUC-AUTOVACUUM-ANALYZE-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_analyze_threshold", "sha256": "a553adbaa0edb4dbdf216a59031edf5974a2791c02e12f3a6f23a0df0cdc59d1"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_analyze_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of inserted, updated or deleted tuples needed to trigger an ANALYZE in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_analyze_threshold = value)", "description": ["Per-table value for autovacuum_analyze_threshold parameter."]}, "12": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_analyze_threshold/?v=12", "label": "Global parameter autovacuum_analyze_threshold"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-AUTOVACUUM-ANALYZE-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/runtime-config-autovacuum.html#GUC-AUTOVACUUM-ANALYZE-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_analyze_threshold", "sha256": "bb486d78e8d17e633e046674781b62e0cf0f77efbb48cd6fffa5fd6b34ac98e6"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_analyze_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of inserted, updated or deleted tuples needed to trigger an ANALYZE in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_analyze_threshold = value)", "description": ["Per-table value for autovacuum_analyze_threshold parameter."]}, "13": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_analyze_threshold/?v=13", "label": "Global parameter autovacuum_analyze_threshold"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-ANALYZE-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-autovacuum.html#GUC-AUTOVACUUM-ANALYZE-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_analyze_threshold", "sha256": "d26d014ad3850d3dbbbc1bce41bc267205baa1523b73e48fdd9e7165b6f6785e"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_analyze_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of inserted, updated or deleted tuples needed to trigger an ANALYZE in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_analyze_threshold = value)", "description": ["Per-table value for autovacuum_analyze_threshold parameter."]}, "14": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_analyze_threshold/?v=14", "label": "Global parameter autovacuum_analyze_threshold"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-ANALYZE-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-autovacuum.html#GUC-AUTOVACUUM-ANALYZE-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_analyze_threshold", "sha256": "03e821969b789b688f725579aa8bd52763880e798ca8680d894f2c12861724cf"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_analyze_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of inserted, updated or deleted tuples needed to trigger an ANALYZE in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_analyze_threshold = value)", "description": ["Per-table value for autovacuum_analyze_threshold parameter."]}, "15": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_analyze_threshold/?v=15", "label": "Global parameter autovacuum_analyze_threshold"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-ANALYZE-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-autovacuum.html#GUC-AUTOVACUUM-ANALYZE-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_analyze_threshold", "sha256": "993bb5fe87856e4c4cb9aedac41232b5915272a65226f57e7fbf0713be2b13f4"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_analyze_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of inserted, updated or deleted tuples needed to trigger an ANALYZE in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_analyze_threshold = value)", "description": ["Per-table value for autovacuum_analyze_threshold parameter."]}, "16": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_analyze_threshold/?v=16", "label": "Global parameter autovacuum_analyze_threshold"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-ANALYZE-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-autovacuum.html#GUC-AUTOVACUUM-ANALYZE-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_analyze_threshold", "sha256": "b16c76b3ffb04e1e6601c44b44e2237f2a97916a52ca9b156a820abdf6545547"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_analyze_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of inserted, updated or deleted tuples needed to trigger an ANALYZE in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_analyze_threshold = value)", "description": ["Per-table value for autovacuum_analyze_threshold parameter."]}, "17": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_analyze_threshold/?v=17", "label": "Global parameter autovacuum_analyze_threshold"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-ANALYZE-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-autovacuum.html#GUC-AUTOVACUUM-ANALYZE-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_analyze_threshold", "sha256": "8caf714d72c9f2ed5f0f8d65041109e0ab8845c7c1169c0febef5193bdaef36d"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_analyze_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of inserted, updated or deleted tuples needed to trigger an ANALYZE in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_analyze_threshold = value)", "description": ["Per-table value for autovacuum_analyze_threshold parameter."]}, "18": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_analyze_threshold/?v=18", "label": "Global parameter autovacuum_analyze_threshold"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-ANALYZE-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-ANALYZE-THRESHOLD", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_analyze_threshold", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_analyze_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of inserted, updated or deleted tuples needed to trigger an ANALYZE in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_analyze_threshold = value)", "description": ["Per-table value for autovacuum_analyze_threshold parameter."]}, "19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_analyze_threshold/?v=19", "label": "Global parameter autovacuum_analyze_threshold"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-ANALYZE-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-AUTOVACUUM-ANALYZE-THRESHOLD", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_analyze_threshold", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_analyze_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of inserted, updated or deleted tuples needed to trigger an ANALYZE in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_analyze_threshold = value)", "description": ["Per-table value for autovacuum_analyze_threshold parameter."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_analyze_threshold/?v=20", "label": "Global parameter autovacuum_analyze_threshold"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-ANALYZE-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-AUTOVACUUM-ANALYZE-THRESHOLD", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_analyze_threshold", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_analyze_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of inserted, updated or deleted tuples needed to trigger an ANALYZE in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_analyze_threshold = value)", "description": ["Per-table value for autovacuum_analyze_threshold parameter."]}}, "content_hash": "ce63fee72509844a7eec7066db52cc93a7d3d7ab9ef77759990cf69a9b4e12b0", "imported_at": "2026-09-27T09:57:58.925", "url": "/wiki/relopts/table-autovacuum-analyze-threshold/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-analyze-threshold/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-analyze-threshold/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-analyze-threshold/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-analyze-threshold/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-analyze-threshold/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-analyze-threshold/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-analyze-threshold/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-analyze-threshold/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-analyze-threshold/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-analyze-threshold/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-analyze-threshold/?v=20"}], "present": true}, {"slug": "table-autovacuum-enabled", "name": "autovacuum_enabled", "name_zh": "autovacuum_enabled", "category": "Tables and materialized views", "summary": "Enables or disables the autovacuum daemon for a particular table. If true, the autovacuum daemon will perform automatic VACUUM and/or ANALYZE operations on this table following the rules discussed in Section 24.1.6 . If false, this table will not be autovacuumed, except to prevent transaction ID wraparound. See Section 24.1.5 for more about wraparound prevention. Note that the autovacuum daemon does not run at all (except to prevent transaction ID wraparound) if the autovacuum parameter is false; setting individual tables' storage parameters does not override that. Therefore there is seldom much point in explicitly setting this storage parameter to true , only to false .", "aliases": ["table.autovacuum_enabled"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}], "signature": "WITH (autovacuum_enabled = value)", "description": ["Enables or disables the autovacuum daemon for a particular table. If true, the autovacuum daemon will perform automatic VACUUM and/or ANALYZE operations on this table following the rules discussed in Section 24.1.6 . If false, this table will not be autovacuumed, except to prevent transaction ID wraparound. See Section 24.1.5 for more about wraparound prevention. Note that the autovacuum daemon does not run at all (except to prevent transaction ID wraparound) if the autovacuum parameter is false; setting individual tables' storage parameters does not override that. Therefore there is seldom much point in explicitly setting this storage parameter to true , only to false ."]}, "11": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}], "signature": "WITH (autovacuum_enabled = value)", "description": ["Enables or disables the autovacuum daemon for a particular table. If true, the autovacuum daemon will perform automatic VACUUM and/or ANALYZE operations on this table following the rules discussed in Section 24.1.6 . If false, this table will not be autovacuumed, except to prevent transaction ID wraparound. See Section 24.1.5 for more about wraparound prevention. Note that the autovacuum daemon does not run at all (except to prevent transaction ID wraparound) if the autovacuum parameter is false; setting individual tables' storage parameters does not override that. Therefore there is seldom much point in explicitly setting this storage parameter to true , only to false ."]}, "12": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-AUTOVACUUM-ENABLED", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (autovacuum_enabled = value)", "description": ["Enables or disables the autovacuum daemon for a particular table. If true, the autovacuum daemon will perform automatic VACUUM and/or ANALYZE operations on this table following the rules discussed in Section 24.1.6 . If false, this table will not be autovacuumed, except to prevent transaction ID wraparound. See Section 24.1.5 for more about wraparound prevention. Note that the autovacuum daemon does not run at all (except to prevent transaction ID wraparound) if the autovacuum parameter is false; setting individual tables' storage parameters does not override that. Therefore there is seldom much point in explicitly setting this storage parameter to true , only to false ."]}, "13": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-ENABLED", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (autovacuum_enabled = value)", "description": ["Enables or disables the autovacuum daemon for a particular table. If true, the autovacuum daemon will perform automatic VACUUM and/or ANALYZE operations on this table following the rules discussed in Section 24.1.6 . If false, this table will not be autovacuumed, except to prevent transaction ID wraparound. See Section 24.1.5 for more about wraparound prevention. Note that the autovacuum daemon does not run at all (except to prevent transaction ID wraparound) if the autovacuum parameter is false; setting individual tables' storage parameters does not override that. Therefore there is seldom much point in explicitly setting this storage parameter to true , only to false ."]}, "14": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-ENABLED", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (autovacuum_enabled = value)", "description": ["Enables or disables the autovacuum daemon for a particular table. If true, the autovacuum daemon will perform automatic VACUUM and/or ANALYZE operations on this table following the rules discussed in Section 25.1.6 . If false, this table will not be autovacuumed, except to prevent transaction ID wraparound. See Section 25.1.5 for more about wraparound prevention. Note that the autovacuum daemon does not run at all (except to prevent transaction ID wraparound) if the autovacuum parameter is false; setting individual tables' storage parameters does not override that. Therefore there is seldom much point in explicitly setting this storage parameter to true , only to false ."]}, "15": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-ENABLED", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (autovacuum_enabled = value)", "description": ["Enables or disables the autovacuum daemon for a particular table. If true, the autovacuum daemon will perform automatic VACUUM and/or ANALYZE operations on this table following the rules discussed in Section 25.1.6 . If false, this table will not be autovacuumed, except to prevent transaction ID wraparound. See Section 25.1.5 for more about wraparound prevention. Note that the autovacuum daemon does not run at all (except to prevent transaction ID wraparound) if the autovacuum parameter is false; setting individual tables' storage parameters does not override that. Therefore there is seldom much point in explicitly setting this storage parameter to true , only to false ."]}, "16": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-ENABLED", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (autovacuum_enabled = value)", "description": ["Enables or disables the autovacuum daemon for a particular table. If true, the autovacuum daemon will perform automatic VACUUM and/or ANALYZE operations on this table following the rules discussed in Section 25.1.6 . If false, this table will not be autovacuumed, except to prevent transaction ID wraparound. See Section 25.1.5 for more about wraparound prevention. Note that the autovacuum daemon does not run at all (except to prevent transaction ID wraparound) if the autovacuum parameter is false; setting individual tables' storage parameters does not override that. Therefore there is seldom much point in explicitly setting this storage parameter to true , only to false ."]}, "17": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-ENABLED", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (autovacuum_enabled = value)", "description": ["Enables or disables the autovacuum daemon for a particular table. If true, the autovacuum daemon will perform automatic VACUUM and/or ANALYZE operations on this table following the rules discussed in Section 24.1.6 . If false, this table will not be autovacuumed, except to prevent transaction ID wraparound. See Section 24.1.5 for more about wraparound prevention. Note that the autovacuum daemon does not run at all (except to prevent transaction ID wraparound) if the autovacuum parameter is false; setting individual tables' storage parameters does not override that. Therefore there is seldom much point in explicitly setting this storage parameter to true , only to false ."]}, "18": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-ENABLED", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (autovacuum_enabled = value)", "description": ["Enables or disables the autovacuum daemon for a particular table. If true, the autovacuum daemon will perform automatic VACUUM and/or ANALYZE operations on this table following the rules discussed in Section 24.1.6 . If false, this table will not be autovacuumed, except to prevent transaction ID wraparound. See Section 24.1.5 for more about wraparound prevention. Note that the autovacuum daemon does not run at all (except to prevent transaction ID wraparound) if the autovacuum parameter is false; setting individual tables' storage parameters does not override that. Therefore there is seldom much point in explicitly setting this storage parameter to true , only to false ."]}, "19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-ENABLED", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (autovacuum_enabled = value)", "description": ["Enables or disables the autovacuum daemon for a particular table. If true, the autovacuum daemon will perform automatic VACUUM and/or ANALYZE operations on this table following the rules discussed in Section 24.1.6 . If false, this table will not be autovacuumed, except to prevent transaction ID wraparound. See Section 24.1.5 for more about wraparound prevention. Note that the autovacuum daemon does not run at all (except to prevent transaction ID wraparound) if the autovacuum parameter is false; setting individual tables' storage parameters does not override that. Therefore there is seldom much point in explicitly setting this storage parameter to true , only to false ."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-ENABLED", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (autovacuum_enabled = value)", "description": ["Enables or disables the autovacuum daemon for a particular table. If true, the autovacuum daemon will perform automatic VACUUM and/or ANALYZE operations on this table following the rules discussed in Section 24.1.6 . If false, this table will not be autovacuumed, except to prevent transaction ID wraparound. See Section 24.1.5 for more about wraparound prevention. Note that the autovacuum daemon does not run at all (except to prevent transaction ID wraparound) if the autovacuum parameter is false; setting individual tables' storage parameters does not override that. Therefore there is seldom much point in explicitly setting this storage parameter to true , only to false ."]}}, "content_hash": "7e9e93e66b5d74ba31c0afc311b2daaf78020ee8bebe49f2c203c09e0ba7f086", "imported_at": "2026-09-27T09:57:58.928", "url": "/wiki/relopts/table-autovacuum-enabled/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-enabled/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-enabled/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-enabled/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-enabled/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-enabled/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-enabled/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-enabled/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-enabled/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-enabled/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-enabled/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-enabled/?v=20"}], "present": true}, {"slug": "table-autovacuum-freeze-max-age", "name": "autovacuum_freeze_max_age", "name_zh": "autovacuum_freeze_max_age", "category": "Tables and materialized views", "summary": "Per-table value for autovacuum_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller).", "aliases": ["table.autovacuum_freeze_max_age"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_freeze_max_age/?v=10", "label": "Global parameter autovacuum_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_freeze_max_age", "sha256": "a8c8d51fd43c0e169a2ce6bcb094c1dbd5f0f6cd6e90cabc86f6542039600355"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in transactions) that a table's pg_class . relfrozenxid field can attain before a VACUUM operation is forced to prevent transaction ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuum also allows removal of old files from the pg_xact subdirectory, which is why the default is a relatively low 200 million transactions. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5 ."]}], "signature": "WITH (autovacuum_freeze_max_age = value)", "description": ["Per-table value for autovacuum_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "11": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_freeze_max_age/?v=11", "label": "Global parameter autovacuum_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_freeze_max_age", "sha256": "a553adbaa0edb4dbdf216a59031edf5974a2791c02e12f3a6f23a0df0cdc59d1"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in transactions) that a table's pg_class . relfrozenxid field can attain before a VACUUM operation is forced to prevent transaction ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuum also allows removal of old files from the pg_xact subdirectory, which is why the default is a relatively low 200 million transactions. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5 ."]}], "signature": "WITH (autovacuum_freeze_max_age = value)", "description": ["Per-table value for autovacuum_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "12": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_freeze_max_age/?v=12", "label": "Global parameter autovacuum_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_freeze_max_age", "sha256": "bb486d78e8d17e633e046674781b62e0cf0f77efbb48cd6fffa5fd6b34ac98e6"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in transactions) that a table's pg_class . relfrozenxid field can attain before a VACUUM operation is forced to prevent transaction ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuum also allows removal of old files from the pg_xact subdirectory, which is why the default is a relatively low 200 million transactions. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5 ."]}], "signature": "WITH (autovacuum_freeze_max_age = value)", "description": ["Per-table value for autovacuum_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "13": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_freeze_max_age/?v=13", "label": "Global parameter autovacuum_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_freeze_max_age", "sha256": "d26d014ad3850d3dbbbc1bce41bc267205baa1523b73e48fdd9e7165b6f6785e"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in transactions) that a table's pg_class . relfrozenxid field can attain before a VACUUM operation is forced to prevent transaction ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuum also allows removal of old files from the pg_xact subdirectory, which is why the default is a relatively low 200 million transactions. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5 ."]}], "signature": "WITH (autovacuum_freeze_max_age = value)", "description": ["Per-table value for autovacuum_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "14": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_freeze_max_age/?v=14", "label": "Global parameter autovacuum_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_freeze_max_age", "sha256": "03e821969b789b688f725579aa8bd52763880e798ca8680d894f2c12861724cf"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in transactions) that a table's pg_class . relfrozenxid field can attain before a VACUUM operation is forced to prevent transaction ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuum also allows removal of old files from the pg_xact subdirectory, which is why the default is a relatively low 200 million transactions. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 25.1.5 ."]}], "signature": "WITH (autovacuum_freeze_max_age = value)", "description": ["Per-table value for autovacuum_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "15": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_freeze_max_age/?v=15", "label": "Global parameter autovacuum_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_freeze_max_age", "sha256": "993bb5fe87856e4c4cb9aedac41232b5915272a65226f57e7fbf0713be2b13f4"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in transactions) that a table's pg_class . relfrozenxid field can attain before a VACUUM operation is forced to prevent transaction ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuum also allows removal of old files from the pg_xact subdirectory, which is why the default is a relatively low 200 million transactions. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 25.1.5 ."]}], "signature": "WITH (autovacuum_freeze_max_age = value)", "description": ["Per-table value for autovacuum_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "16": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_freeze_max_age/?v=16", "label": "Global parameter autovacuum_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_freeze_max_age", "sha256": "b16c76b3ffb04e1e6601c44b44e2237f2a97916a52ca9b156a820abdf6545547"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in transactions) that a table's pg_class . relfrozenxid field can attain before a VACUUM operation is forced to prevent transaction ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuum also allows removal of old files from the pg_xact subdirectory, which is why the default is a relatively low 200 million transactions. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 25.1.5 ."]}], "signature": "WITH (autovacuum_freeze_max_age = value)", "description": ["Per-table value for autovacuum_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "17": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_freeze_max_age/?v=17", "label": "Global parameter autovacuum_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_freeze_max_age", "sha256": "8caf714d72c9f2ed5f0f8d65041109e0ab8845c7c1169c0febef5193bdaef36d"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in transactions) that a table's pg_class . relfrozenxid field can attain before a VACUUM operation is forced to prevent transaction ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuum also allows removal of old files from the pg_xact subdirectory, which is why the default is a relatively low 200 million transactions. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5 ."]}], "signature": "WITH (autovacuum_freeze_max_age = value)", "description": ["Per-table value for autovacuum_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "18": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_freeze_max_age/?v=18", "label": "Global parameter autovacuum_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_freeze_max_age", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in transactions) that a table's pg_class . relfrozenxid field can attain before a VACUUM operation is forced to prevent transaction ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuum also allows removal of old files from the pg_xact subdirectory, which is why the default is a relatively low 200 million transactions. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5 ."]}], "signature": "WITH (autovacuum_freeze_max_age = value)", "description": ["Per-table value for autovacuum_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_freeze_max_age/?v=19", "label": "Global parameter autovacuum_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_freeze_max_age", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in transactions) that a table's pg_class . relfrozenxid field can attain before a VACUUM operation is forced to prevent transaction ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuum also allows removal of old files from the pg_xact subdirectory, which is why the default is a relatively low 200 million transactions. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5 ."]}], "signature": "WITH (autovacuum_freeze_max_age = value)", "description": ["Per-table value for autovacuum_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_freeze_max_age/?v=20", "label": "Global parameter autovacuum_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_freeze_max_age", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in transactions) that a table's pg_class . relfrozenxid field can attain before a VACUUM operation is forced to prevent transaction ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuum also allows removal of old files from the pg_xact subdirectory, which is why the default is a relatively low 200 million transactions. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5 ."]}], "signature": "WITH (autovacuum_freeze_max_age = value)", "description": ["Per-table value for autovacuum_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}}, "content_hash": "7dbae7b09d80c7a2b87d8a2878d2fa455aa825b030584023b81ac156f4845683", "imported_at": "2026-09-27T09:57:58.930", "url": "/wiki/relopts/table-autovacuum-freeze-max-age/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-max-age/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-max-age/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-max-age/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-max-age/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-max-age/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-max-age/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-max-age/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-max-age/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-max-age/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-max-age/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-max-age/?v=20"}], "present": true}, {"slug": "table-autovacuum-freeze-min-age", "name": "autovacuum_freeze_min_age", "name_zh": "autovacuum_freeze_min_age", "category": "Tables and materialized views", "summary": "Per-table value for vacuum_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_min_age parameters that are larger than half the system-wide autovacuum_freeze_max_age setting.", "aliases": ["table.autovacuum_freeze_min_age"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_freeze_min_age/?v=10", "label": "Global parameter vacuum_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/runtime-config-client.html#GUC-VACUUM-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_min_age", "sha256": "81c199a46b03a65a060e25cf874fc7ddd28b18261a6472a912954073556935b4"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in transactions) that VACUUM should use to decide whether to freeze row versions while scanning a table. The default is 50 million transactions. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5 ."]}], "signature": "WITH (autovacuum_freeze_min_age = value)", "description": ["Per-table value for vacuum_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_min_age parameters that are larger than half the system-wide autovacuum_freeze_max_age setting."]}, "11": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_freeze_min_age/?v=11", "label": "Global parameter vacuum_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/runtime-config-client.html#GUC-VACUUM-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_min_age", "sha256": "488947b3f6c09ac9a815b8602e852239936b403ef214249fee7aeca1469c25ba"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in transactions) that VACUUM should use to decide whether to freeze row versions while scanning a table. The default is 50 million transactions. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5 ."]}], "signature": "WITH (autovacuum_freeze_min_age = value)", "description": ["Per-table value for vacuum_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_min_age parameters that are larger than half the system-wide autovacuum_freeze_max_age setting."]}, "12": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_freeze_min_age/?v=12", "label": "Global parameter vacuum_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/runtime-config-client.html#GUC-VACUUM-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_min_age", "sha256": "7f27882cdde3b36cef070cdd14ce3f080b65ed837d3f6b41f3faf454ba89cc63"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in transactions) that VACUUM should use to decide whether to freeze row versions while scanning a table. The default is 50 million transactions. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5 ."]}], "signature": "WITH (autovacuum_freeze_min_age = value)", "description": ["Per-table value for vacuum_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_min_age parameters that are larger than half the system-wide autovacuum_freeze_max_age setting."]}, "13": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_freeze_min_age/?v=13", "label": "Global parameter vacuum_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-client.html#GUC-VACUUM-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_min_age", "sha256": "5d70022f2524a39e7c5745698de51d867f687c70394779ad154e05648e923c7d"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in transactions) that VACUUM should use to decide whether to freeze row versions while scanning a table. The default is 50 million transactions. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5 ."]}], "signature": "WITH (autovacuum_freeze_min_age = value)", "description": ["Per-table value for vacuum_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_min_age parameters that are larger than half the system-wide autovacuum_freeze_max_age setting."]}, "14": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_freeze_min_age/?v=14", "label": "Global parameter vacuum_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-client.html#GUC-VACUUM-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_min_age", "sha256": "35d48bb20f151039202a7cafbe7c4ffb109262110d62b2ab75844a3d80c2cebb"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in transactions) that VACUUM should use to decide whether to freeze row versions while scanning a table. The default is 50 million transactions. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 25.1.5 ."]}], "signature": "WITH (autovacuum_freeze_min_age = value)", "description": ["Per-table value for vacuum_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_min_age parameters that are larger than half the system-wide autovacuum_freeze_max_age setting."]}, "15": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_freeze_min_age/?v=15", "label": "Global parameter vacuum_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-client.html#GUC-VACUUM-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_min_age", "sha256": "fdcf588ddeeac62758840aa3b8d6ead7e37e1b0c72795e339f67db5b23509462"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in transactions) that VACUUM should use to decide whether to freeze row versions while scanning a table. The default is 50 million transactions. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 25.1.5 ."]}], "signature": "WITH (autovacuum_freeze_min_age = value)", "description": ["Per-table value for vacuum_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_min_age parameters that are larger than half the system-wide autovacuum_freeze_max_age setting."]}, "16": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_freeze_min_age/?v=16", "label": "Global parameter vacuum_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-client.html#GUC-VACUUM-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_min_age", "sha256": "e7e096464bd87b0bfc06652cdbbdd175f7a0e955207580049eae2ee394566b20"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in transactions) that VACUUM should use to decide whether to trigger freezing of pages that have an older XID. The default is 50 million transactions. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 25.1.5 ."]}], "signature": "WITH (autovacuum_freeze_min_age = value)", "description": ["Per-table value for vacuum_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_min_age parameters that are larger than half the system-wide autovacuum_freeze_max_age setting."]}, "17": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_freeze_min_age/?v=17", "label": "Global parameter vacuum_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-client.html#GUC-VACUUM-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_min_age", "sha256": "e7ba41a33997d251c23f06ccf17978bf1481db92a2c607026f59af86c25d6f50"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in transactions) that VACUUM should use to decide whether to trigger freezing of pages that have an older XID. The default is 50 million transactions. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5 ."]}], "signature": "WITH (autovacuum_freeze_min_age = value)", "description": ["Per-table value for vacuum_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_min_age parameters that are larger than half the system-wide autovacuum_freeze_max_age setting."]}, "18": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_freeze_min_age/?v=18", "label": "Global parameter vacuum_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-VACUUM-FREEZE-MIN-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_freeze_min_age", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in transactions) that VACUUM should use to decide whether to trigger freezing of pages that have an older XID. The default is 50 million transactions. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5 ."]}], "signature": "WITH (autovacuum_freeze_min_age = value)", "description": ["Per-table value for vacuum_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_min_age parameters that are larger than half the system-wide autovacuum_freeze_max_age setting."]}, "19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_freeze_min_age/?v=19", "label": "Global parameter vacuum_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-VACUUM-FREEZE-MIN-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_freeze_min_age", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in transactions) that VACUUM should use to decide whether to trigger freezing of pages that have an older XID. The default is 50 million transactions. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5 ."]}], "signature": "WITH (autovacuum_freeze_min_age = value)", "description": ["Per-table value for vacuum_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_min_age parameters that are larger than half the system-wide autovacuum_freeze_max_age setting."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_freeze_min_age/?v=20", "label": "Global parameter vacuum_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-VACUUM-FREEZE-MIN-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_freeze_min_age", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in transactions) that VACUUM should use to decide whether to trigger freezing of pages that have an older XID. The default is 50 million transactions. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5 ."]}], "signature": "WITH (autovacuum_freeze_min_age = value)", "description": ["Per-table value for vacuum_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_freeze_min_age parameters that are larger than half the system-wide autovacuum_freeze_max_age setting."]}}, "content_hash": "dfc26ea3afc944727379348c8174068a860c108f63875a69650f3ff708157a6a", "imported_at": "2026-09-27T09:57:58.932", "url": "/wiki/relopts/table-autovacuum-freeze-min-age/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-min-age/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-min-age/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-min-age/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-min-age/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-min-age/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-min-age/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-min-age/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-min-age/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-min-age/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-min-age/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-min-age/?v=20"}], "present": true}, {"slug": "table-autovacuum-freeze-table-age", "name": "autovacuum_freeze_table_age", "name_zh": "autovacuum_freeze_table_age", "category": "Tables and materialized views", "summary": "Per-table value for vacuum_freeze_table_age parameter.", "aliases": ["table.autovacuum_freeze_table_age"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_freeze_table_age/?v=10", "label": "Global parameter vacuum_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/runtime-config-client.html#GUC-VACUUM-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_table_age", "sha256": "81c199a46b03a65a060e25cf874fc7ddd28b18261a6472a912954073556935b4"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relfrozenxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million transactions. Although users can set this value anywhere from zero to two billions, VACUUM will silently limit the effective value to 95% of autovacuum_freeze_max_age , so that a periodical manual VACUUM has a chance to run before an anti-wraparound autovacuum is launched for the table. For more information see Section 24.1.5 ."]}], "signature": "WITH (autovacuum_freeze_table_age = value)", "description": ["Per-table value for vacuum_freeze_table_age parameter."]}, "11": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_freeze_table_age/?v=11", "label": "Global parameter vacuum_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/runtime-config-client.html#GUC-VACUUM-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_table_age", "sha256": "488947b3f6c09ac9a815b8602e852239936b403ef214249fee7aeca1469c25ba"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relfrozenxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million transactions. Although users can set this value anywhere from zero to two billions, VACUUM will silently limit the effective value to 95% of autovacuum_freeze_max_age , so that a periodical manual VACUUM has a chance to run before an anti-wraparound autovacuum is launched for the table. For more information see Section 24.1.5 ."]}], "signature": "WITH (autovacuum_freeze_table_age = value)", "description": ["Per-table value for vacuum_freeze_table_age parameter."]}, "12": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_freeze_table_age/?v=12", "label": "Global parameter vacuum_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/runtime-config-client.html#GUC-VACUUM-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_table_age", "sha256": "7f27882cdde3b36cef070cdd14ce3f080b65ed837d3f6b41f3faf454ba89cc63"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relfrozenxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million transactions. Although users can set this value anywhere from zero to two billions, VACUUM will silently limit the effective value to 95% of autovacuum_freeze_max_age , so that a periodical manual VACUUM has a chance to run before an anti-wraparound autovacuum is launched for the table. For more information see Section 24.1.5 ."]}], "signature": "WITH (autovacuum_freeze_table_age = value)", "description": ["Per-table value for vacuum_freeze_table_age parameter."]}, "13": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_freeze_table_age/?v=13", "label": "Global parameter vacuum_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-client.html#GUC-VACUUM-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_table_age", "sha256": "5d70022f2524a39e7c5745698de51d867f687c70394779ad154e05648e923c7d"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relfrozenxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million transactions. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound autovacuum is launched for the table. For more information see Section 24.1.5 ."]}], "signature": "WITH (autovacuum_freeze_table_age = value)", "description": ["Per-table value for vacuum_freeze_table_age parameter."]}, "14": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_freeze_table_age/?v=14", "label": "Global parameter vacuum_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-client.html#GUC-VACUUM-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_table_age", "sha256": "35d48bb20f151039202a7cafbe7c4ffb109262110d62b2ab75844a3d80c2cebb"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relfrozenxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million transactions. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound autovacuum is launched for the table. For more information see Section 25.1.5 ."]}], "signature": "WITH (autovacuum_freeze_table_age = value)", "description": ["Per-table value for vacuum_freeze_table_age parameter."]}, "15": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_freeze_table_age/?v=15", "label": "Global parameter vacuum_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-client.html#GUC-VACUUM-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_table_age", "sha256": "fdcf588ddeeac62758840aa3b8d6ead7e37e1b0c72795e339f67db5b23509462"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relfrozenxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million transactions. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound autovacuum is launched for the table. For more information see Section 25.1.5 ."]}], "signature": "WITH (autovacuum_freeze_table_age = value)", "description": ["Per-table value for vacuum_freeze_table_age parameter."]}, "16": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_freeze_table_age/?v=16", "label": "Global parameter vacuum_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-client.html#GUC-VACUUM-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_table_age", "sha256": "e7e096464bd87b0bfc06652cdbbdd175f7a0e955207580049eae2ee394566b20"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relfrozenxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million transactions. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound autovacuum is launched for the table. For more information see Section 25.1.5 ."]}], "signature": "WITH (autovacuum_freeze_table_age = value)", "description": ["Per-table value for vacuum_freeze_table_age parameter."]}, "17": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_freeze_table_age/?v=17", "label": "Global parameter vacuum_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-client.html#GUC-VACUUM-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_freeze_table_age", "sha256": "e7ba41a33997d251c23f06ccf17978bf1481db92a2c607026f59af86c25d6f50"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relfrozenxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million transactions. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound autovacuum is launched for the table. For more information see Section 24.1.5 ."]}], "signature": "WITH (autovacuum_freeze_table_age = value)", "description": ["Per-table value for vacuum_freeze_table_age parameter."]}, "18": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_freeze_table_age/?v=18", "label": "Global parameter vacuum_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-VACUUM-FREEZE-TABLE-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_freeze_table_age", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relfrozenxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million transactions. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound autovacuum is launched for the table. For more information see Section 24.1.5 ."]}], "signature": "WITH (autovacuum_freeze_table_age = value)", "description": ["Per-table value for vacuum_freeze_table_age parameter."]}, "19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_freeze_table_age/?v=19", "label": "Global parameter vacuum_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-VACUUM-FREEZE-TABLE-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_freeze_table_age", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relfrozenxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million transactions. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound autovacuum is launched for the table. For more information see Section 24.1.5 ."]}], "signature": "WITH (autovacuum_freeze_table_age = value)", "description": ["Per-table value for vacuum_freeze_table_age parameter."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_freeze_table_age/?v=20", "label": "Global parameter vacuum_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-VACUUM-FREEZE-TABLE-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_freeze_table_age", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relfrozenxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million transactions. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound autovacuum is launched for the table. For more information see Section 24.1.5 ."]}], "signature": "WITH (autovacuum_freeze_table_age = value)", "description": ["Per-table value for vacuum_freeze_table_age parameter."]}}, "content_hash": "6960a46877a0f4718211a710e75e253938a19f33fbcf310e580811840071c389", "imported_at": "2026-09-27T09:57:58.935", "url": "/wiki/relopts/table-autovacuum-freeze-table-age/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-table-age/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-table-age/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-table-age/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-table-age/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-table-age/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-table-age/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-table-age/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-table-age/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-table-age/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-table-age/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-freeze-table-age/?v=20"}], "present": true}, {"slug": "table-autovacuum-multixact-freeze-max-age", "name": "autovacuum_multixact_freeze_max_age", "name_zh": "autovacuum_multixact_freeze_max_age", "category": "Tables and materialized views", "summary": "Per-table value for autovacuum_multixact_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller).", "aliases": ["table.autovacuum_multixact_freeze_max_age"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_multixact_freeze_max_age/?v=10", "label": "Global parameter autovacuum_multixact_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/runtime-config-autovacuum.html#GUC-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_multixact_freeze_max_age", "sha256": "a8c8d51fd43c0e169a2ce6bcb094c1dbd5f0f6cd6e90cabc86f6542039600355"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_multixact_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in multixacts) that a table's pg_class . relminmxid field can attain before a VACUUM operation is forced to prevent multixact ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuuming multixacts also allows removal of old files from the pg_multixact/members and pg_multixact/offsets subdirectories, which is why the default is a relatively low 400 million multixacts. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_max_age = value)", "description": ["Per-table value for autovacuum_multixact_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "11": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_multixact_freeze_max_age/?v=11", "label": "Global parameter autovacuum_multixact_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/runtime-config-autovacuum.html#GUC-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_multixact_freeze_max_age", "sha256": "a553adbaa0edb4dbdf216a59031edf5974a2791c02e12f3a6f23a0df0cdc59d1"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_multixact_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in multixacts) that a table's pg_class . relminmxid field can attain before a VACUUM operation is forced to prevent multixact ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuuming multixacts also allows removal of old files from the pg_multixact/members and pg_multixact/offsets subdirectories, which is why the default is a relatively low 400 million multixacts. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_max_age = value)", "description": ["Per-table value for autovacuum_multixact_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "12": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_multixact_freeze_max_age/?v=12", "label": "Global parameter autovacuum_multixact_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/runtime-config-autovacuum.html#GUC-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_multixact_freeze_max_age", "sha256": "bb486d78e8d17e633e046674781b62e0cf0f77efbb48cd6fffa5fd6b34ac98e6"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_multixact_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in multixacts) that a table's pg_class . relminmxid field can attain before a VACUUM operation is forced to prevent multixact ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuuming multixacts also allows removal of old files from the pg_multixact/members and pg_multixact/offsets subdirectories, which is why the default is a relatively low 400 million multixacts. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_max_age = value)", "description": ["Per-table value for autovacuum_multixact_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "13": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_multixact_freeze_max_age/?v=13", "label": "Global parameter autovacuum_multixact_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-autovacuum.html#GUC-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_multixact_freeze_max_age", "sha256": "d26d014ad3850d3dbbbc1bce41bc267205baa1523b73e48fdd9e7165b6f6785e"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_multixact_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in multixacts) that a table's pg_class . relminmxid field can attain before a VACUUM operation is forced to prevent multixact ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuuming multixacts also allows removal of old files from the pg_multixact/members and pg_multixact/offsets subdirectories, which is why the default is a relatively low 400 million multixacts. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_max_age = value)", "description": ["Per-table value for autovacuum_multixact_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "14": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_multixact_freeze_max_age/?v=14", "label": "Global parameter autovacuum_multixact_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-autovacuum.html#GUC-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_multixact_freeze_max_age", "sha256": "03e821969b789b688f725579aa8bd52763880e798ca8680d894f2c12861724cf"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_multixact_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in multixacts) that a table's pg_class . relminmxid field can attain before a VACUUM operation is forced to prevent multixact ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuuming multixacts also allows removal of old files from the pg_multixact/members and pg_multixact/offsets subdirectories, which is why the default is a relatively low 400 million multixacts. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 25.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_max_age = value)", "description": ["Per-table value for autovacuum_multixact_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "15": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_multixact_freeze_max_age/?v=15", "label": "Global parameter autovacuum_multixact_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-autovacuum.html#GUC-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_multixact_freeze_max_age", "sha256": "993bb5fe87856e4c4cb9aedac41232b5915272a65226f57e7fbf0713be2b13f4"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_multixact_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in multixacts) that a table's pg_class . relminmxid field can attain before a VACUUM operation is forced to prevent multixact ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuuming multixacts also allows removal of old files from the pg_multixact/members and pg_multixact/offsets subdirectories, which is why the default is a relatively low 400 million multixacts. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 25.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_max_age = value)", "description": ["Per-table value for autovacuum_multixact_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "16": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_multixact_freeze_max_age/?v=16", "label": "Global parameter autovacuum_multixact_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-autovacuum.html#GUC-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_multixact_freeze_max_age", "sha256": "b16c76b3ffb04e1e6601c44b44e2237f2a97916a52ca9b156a820abdf6545547"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_multixact_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in multixacts) that a table's pg_class . relminmxid field can attain before a VACUUM operation is forced to prevent multixact ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuuming multixacts also allows removal of old files from the pg_multixact/members and pg_multixact/offsets subdirectories, which is why the default is a relatively low 400 million multixacts. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 25.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_max_age = value)", "description": ["Per-table value for autovacuum_multixact_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "17": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_multixact_freeze_max_age/?v=17", "label": "Global parameter autovacuum_multixact_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-autovacuum.html#GUC-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_multixact_freeze_max_age", "sha256": "8caf714d72c9f2ed5f0f8d65041109e0ab8845c7c1169c0febef5193bdaef36d"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_multixact_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in multixacts) that a table's pg_class . relminmxid field can attain before a VACUUM operation is forced to prevent multixact ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuuming multixacts also allows removal of old files from the pg_multixact/members and pg_multixact/offsets subdirectories, which is why the default is a relatively low 400 million multixacts. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_max_age = value)", "description": ["Per-table value for autovacuum_multixact_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "18": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_multixact_freeze_max_age/?v=18", "label": "Global parameter autovacuum_multixact_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_multixact_freeze_max_age", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_multixact_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in multixacts) that a table's pg_class . relminmxid field can attain before a VACUUM operation is forced to prevent multixact ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuuming multixacts also allows removal of old files from the pg_multixact/members and pg_multixact/offsets subdirectories, which is why the default is a relatively low 400 million multixacts. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_max_age = value)", "description": ["Per-table value for autovacuum_multixact_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_multixact_freeze_max_age/?v=19", "label": "Global parameter autovacuum_multixact_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_multixact_freeze_max_age", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_multixact_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in multixacts) that a table's pg_class . relminmxid field can attain before a VACUUM operation is forced to prevent multixact ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuuming multixacts also allows removal of old files from the pg_multixact/members and pg_multixact/offsets subdirectories, which is why the default is a relatively low 400 million multixacts. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_max_age = value)", "description": ["Per-table value for autovacuum_multixact_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_multixact_freeze_max_age/?v=20", "label": "Global parameter autovacuum_multixact_freeze_max_age"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_multixact_freeze_max_age", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_multixact_freeze_max_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum age (in multixacts) that a table's pg_class . relminmxid field can attain before a VACUUM operation is forced to prevent multixact ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled.", "Vacuuming multixacts also allows removal of old files from the pg_multixact/members and pg_multixact/offsets subdirectories, which is why the default is a relatively low 400 million multixacts. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing table storage parameters. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_max_age = value)", "description": ["Per-table value for autovacuum_multixact_freeze_max_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_max_age parameters that are larger than the system-wide setting (it can only be set smaller)."]}}, "content_hash": "11a7201ed1bab6ca4b45b28f9114518cfe24eb319739bd4347b62b16a29de0bc", "imported_at": "2026-09-27T09:57:58.937", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-max-age/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-max-age/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-max-age/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-max-age/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-max-age/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-max-age/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-max-age/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-max-age/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-max-age/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-max-age/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-max-age/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-max-age/?v=20"}], "present": true}, {"slug": "table-autovacuum-multixact-freeze-min-age", "name": "autovacuum_multixact_freeze_min_age", "name_zh": "autovacuum_multixact_freeze_min_age", "category": "Tables and materialized views", "summary": "Per-table value for vacuum_multixact_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_min_age parameters that are larger than half the system-wide autovacuum_multixact_freeze_max_age setting.", "aliases": ["table.autovacuum_multixact_freeze_min_age"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_multixact_freeze_min_age/?v=10", "label": "Global parameter vacuum_multixact_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_min_age", "sha256": "81c199a46b03a65a060e25cf874fc7ddd28b18261a6472a912954073556935b4"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in multixacts) that VACUUM should use to decide whether to replace multixact IDs with a newer transaction ID or multixact ID while scanning a table. The default is 5 million multixacts. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_multixact_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_min_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_min_age parameters that are larger than half the system-wide autovacuum_multixact_freeze_max_age setting."]}, "11": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_multixact_freeze_min_age/?v=11", "label": "Global parameter vacuum_multixact_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_min_age", "sha256": "488947b3f6c09ac9a815b8602e852239936b403ef214249fee7aeca1469c25ba"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in multixacts) that VACUUM should use to decide whether to replace multixact IDs with a newer transaction ID or multixact ID while scanning a table. The default is 5 million multixacts. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_multixact_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_min_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_min_age parameters that are larger than half the system-wide autovacuum_multixact_freeze_max_age setting."]}, "12": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_multixact_freeze_min_age/?v=12", "label": "Global parameter vacuum_multixact_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_min_age", "sha256": "7f27882cdde3b36cef070cdd14ce3f080b65ed837d3f6b41f3faf454ba89cc63"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in multixacts) that VACUUM should use to decide whether to replace multixact IDs with a newer transaction ID or multixact ID while scanning a table. The default is 5 million multixacts. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_multixact_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_min_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_min_age parameters that are larger than half the system-wide autovacuum_multixact_freeze_max_age setting."]}, "13": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_multixact_freeze_min_age/?v=13", "label": "Global parameter vacuum_multixact_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_min_age", "sha256": "5d70022f2524a39e7c5745698de51d867f687c70394779ad154e05648e923c7d"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in multixacts) that VACUUM should use to decide whether to replace multixact IDs with a newer transaction ID or multixact ID while scanning a table. The default is 5 million multixacts. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_multixact_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_min_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_min_age parameters that are larger than half the system-wide autovacuum_multixact_freeze_max_age setting."]}, "14": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_multixact_freeze_min_age/?v=14", "label": "Global parameter vacuum_multixact_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_min_age", "sha256": "35d48bb20f151039202a7cafbe7c4ffb109262110d62b2ab75844a3d80c2cebb"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in multixacts) that VACUUM should use to decide whether to replace multixact IDs with a newer transaction ID or multixact ID while scanning a table. The default is 5 million multixacts. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_multixact_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 25.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_min_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_min_age parameters that are larger than half the system-wide autovacuum_multixact_freeze_max_age setting."]}, "15": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_multixact_freeze_min_age/?v=15", "label": "Global parameter vacuum_multixact_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_min_age", "sha256": "fdcf588ddeeac62758840aa3b8d6ead7e37e1b0c72795e339f67db5b23509462"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in multixacts) that VACUUM should use to decide whether to replace multixact IDs with a newer transaction ID or multixact ID while scanning a table. The default is 5 million multixacts. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_multixact_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 25.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_min_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_min_age parameters that are larger than half the system-wide autovacuum_multixact_freeze_max_age setting."]}, "16": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_multixact_freeze_min_age/?v=16", "label": "Global parameter vacuum_multixact_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_min_age", "sha256": "e7e096464bd87b0bfc06652cdbbdd175f7a0e955207580049eae2ee394566b20"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in multixacts) that VACUUM should use to decide whether to trigger freezing of pages with an older multixact ID. The default is 5 million multixacts. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_multixact_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 25.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_min_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_min_age parameters that are larger than half the system-wide autovacuum_multixact_freeze_max_age setting."]}, "17": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_multixact_freeze_min_age/?v=17", "label": "Global parameter vacuum_multixact_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_min_age", "sha256": "e7ba41a33997d251c23f06ccf17978bf1481db92a2c607026f59af86c25d6f50"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in multixacts) that VACUUM should use to decide whether to trigger freezing of pages with an older multixact ID. The default is 5 million multixacts. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_multixact_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_min_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_min_age parameters that are larger than half the system-wide autovacuum_multixact_freeze_max_age setting."]}, "18": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_multixact_freeze_min_age/?v=18", "label": "Global parameter vacuum_multixact_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-VACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_multixact_freeze_min_age", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in multixacts) that VACUUM should use to decide whether to trigger freezing of pages with an older multixact ID. The default is 5 million multixacts. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_multixact_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_min_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_min_age parameters that are larger than half the system-wide autovacuum_multixact_freeze_max_age setting."]}, "19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_multixact_freeze_min_age/?v=19", "label": "Global parameter vacuum_multixact_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-VACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_multixact_freeze_min_age", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in multixacts) that VACUUM should use to decide whether to trigger freezing of pages with an older multixact ID. The default is 5 million multixacts. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_multixact_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_min_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_min_age parameters that are larger than half the system-wide autovacuum_multixact_freeze_max_age setting."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_multixact_freeze_min_age/?v=20", "label": "Global parameter vacuum_multixact_freeze_min_age"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-VACUUM-MULTIXACT-FREEZE-MIN-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_multixact_freeze_min_age", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_min_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cutoff age (in multixacts) that VACUUM should use to decide whether to trigger freezing of pages with an older multixact ID. The default is 5 million multixacts. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_multixact_freeze_max_age , so that there is not an unreasonably short time between forced autovacuums. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_min_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_min_age parameter. Note that autovacuum will ignore per-table autovacuum_multixact_freeze_min_age parameters that are larger than half the system-wide autovacuum_multixact_freeze_max_age setting."]}}, "content_hash": "d0448d3a25a3a0391dae8dada5447140e45e5a9b60328b0e8e687155d95b8249", "imported_at": "2026-09-27T09:57:58.940", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-min-age/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-min-age/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-min-age/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-min-age/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-min-age/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-min-age/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-min-age/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-min-age/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-min-age/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-min-age/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-min-age/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-min-age/?v=20"}], "present": true}, {"slug": "table-autovacuum-multixact-freeze-table-age", "name": "autovacuum_multixact_freeze_table_age", "name_zh": "autovacuum_multixact_freeze_table_age", "category": "Tables and materialized views", "summary": "Per-table value for vacuum_multixact_freeze_table_age parameter.", "aliases": ["table.autovacuum_multixact_freeze_table_age"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_multixact_freeze_table_age/?v=10", "label": "Global parameter vacuum_multixact_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_table_age", "sha256": "81c199a46b03a65a060e25cf874fc7ddd28b18261a6472a912954073556935b4"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relminmxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million multixacts. Although users can set this value anywhere from zero to two billions, VACUUM will silently limit the effective value to 95% of autovacuum_multixact_freeze_max_age , so that a periodical manual VACUUM has a chance to run before an anti-wraparound is launched for the table. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_table_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_table_age parameter."]}, "11": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_multixact_freeze_table_age/?v=11", "label": "Global parameter vacuum_multixact_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_table_age", "sha256": "488947b3f6c09ac9a815b8602e852239936b403ef214249fee7aeca1469c25ba"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relminmxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million multixacts. Although users can set this value anywhere from zero to two billions, VACUUM will silently limit the effective value to 95% of autovacuum_multixact_freeze_max_age , so that a periodical manual VACUUM has a chance to run before an anti-wraparound is launched for the table. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_table_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_table_age parameter."]}, "12": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_multixact_freeze_table_age/?v=12", "label": "Global parameter vacuum_multixact_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_table_age", "sha256": "7f27882cdde3b36cef070cdd14ce3f080b65ed837d3f6b41f3faf454ba89cc63"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relminmxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million multixacts. Although users can set this value anywhere from zero to two billions, VACUUM will silently limit the effective value to 95% of autovacuum_multixact_freeze_max_age , so that a periodical manual VACUUM has a chance to run before an anti-wraparound is launched for the table. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_table_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_table_age parameter."]}, "13": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_multixact_freeze_table_age/?v=13", "label": "Global parameter vacuum_multixact_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_table_age", "sha256": "5d70022f2524a39e7c5745698de51d867f687c70394779ad154e05648e923c7d"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relminmxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million multixacts. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_multixact_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound is launched for the table. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_table_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_table_age parameter."]}, "14": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_multixact_freeze_table_age/?v=14", "label": "Global parameter vacuum_multixact_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_table_age", "sha256": "35d48bb20f151039202a7cafbe7c4ffb109262110d62b2ab75844a3d80c2cebb"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relminmxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million multixacts. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_multixact_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound is launched for the table. For more information see Section 25.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_table_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_table_age parameter."]}, "15": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_multixact_freeze_table_age/?v=15", "label": "Global parameter vacuum_multixact_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_table_age", "sha256": "fdcf588ddeeac62758840aa3b8d6ead7e37e1b0c72795e339f67db5b23509462"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relminmxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million multixacts. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_multixact_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound is launched for the table. For more information see Section 25.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_table_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_table_age parameter."]}, "16": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_multixact_freeze_table_age/?v=16", "label": "Global parameter vacuum_multixact_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_table_age", "sha256": "e7e096464bd87b0bfc06652cdbbdd175f7a0e955207580049eae2ee394566b20"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relminmxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million multixacts. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_multixact_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound is launched for the table. For more information see Section 25.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_table_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_table_age parameter."]}, "17": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_multixact_freeze_table_age/?v=17", "label": "Global parameter vacuum_multixact_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-client.html#GUC-VACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "runtime-config-client.html", "label": "Related global parameter: vacuum_multixact_freeze_table_age", "sha256": "e7ba41a33997d251c23f06ccf17978bf1481db92a2c607026f59af86c25d6f50"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relminmxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million multixacts. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_multixact_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound is launched for the table. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_table_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_table_age parameter."]}, "18": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_multixact_freeze_table_age/?v=18", "label": "Global parameter vacuum_multixact_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-VACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_multixact_freeze_table_age", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relminmxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million multixacts. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_multixact_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound is launched for the table. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_table_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_table_age parameter."]}, "19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_multixact_freeze_table_age/?v=19", "label": "Global parameter vacuum_multixact_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-VACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_multixact_freeze_table_age", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relminmxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million multixacts. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_multixact_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound is launched for the table. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_table_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_table_age parameter."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/vacuum_multixact_freeze_table_age/?v=20", "label": "Global parameter vacuum_multixact_freeze_table_age"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-VACUUM-MULTIXACT-FREEZE-TABLE-AGE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_multixact_freeze_table_age", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_multixact_freeze_table_age", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "VACUUM performs an aggressive scan if the table's pg_class . relminmxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million multixacts. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_multixact_freeze_max_age , so that a periodic manual VACUUM has a chance to run before an anti-wraparound is launched for the table. For more information see Section 24.1.5.1 ."]}], "signature": "WITH (autovacuum_multixact_freeze_table_age = value)", "description": ["Per-table value for vacuum_multixact_freeze_table_age parameter."]}}, "content_hash": "33373ae4f2ecb853e5afc766c05b393401cdc03d6865d54f8b6d275acfb3e527", "imported_at": "2026-09-27T09:57:58.942", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-table-age/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-table-age/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-table-age/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-table-age/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-table-age/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-table-age/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-table-age/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-table-age/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-table-age/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-table-age/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-table-age/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-multixact-freeze-table-age/?v=20"}], "present": true}, {"slug": "table-autovacuum-parallel-workers", "name": "autovacuum_parallel_workers", "name_zh": "autovacuum_parallel_workers", "category": "Tables and materialized views", "summary": "Not recorded in the selected version.", "aliases": ["table.autovacuum_parallel_workers"], "versions": {"19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_max_parallel_workers/?v=19", "label": "Global parameter autovacuum_max_parallel_workers"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-PARALLEL-WORKERS", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-AUTOVACUUM-MAX-PARALLEL-WORKERS", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_max_parallel_workers", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_max_parallel_workers", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Sets the maximum number of parallel workers that can be used by a single autovacuum worker to process indexes. This limit applies specifically to the index vacuuming and index cleanup phases (for the details of each autovacuum phase, please refer to Table 27.51 ). The actual number of parallel workers is further limited by max_parallel_workers . This is the per-autovacuum worker equivalent of the PARALLEL option of the VACUUM command. Setting this value to 0 disables parallel vacuum during autovacuum. The default is 0."]}], "signature": "WITH (autovacuum_parallel_workers = value)", "description": ["Per-table value for autovacuum_max_parallel_workers parameter. If -1 is specified, autovacuum_max_parallel_workers value will be used. If set to 0, parallel vacuum is disabled for this table. The default value is -1."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_max_parallel_workers/?v=20", "label": "Global parameter autovacuum_max_parallel_workers"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-PARALLEL-WORKERS", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-AUTOVACUUM-MAX-PARALLEL-WORKERS", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_max_parallel_workers", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_max_parallel_workers", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Sets the maximum number of parallel workers that can be used by a single autovacuum worker to process indexes. This limit applies specifically to the index vacuuming and index cleanup phases (for the details of each autovacuum phase, please refer to Table 27.52 ). The actual number of parallel workers is further limited by max_parallel_workers . This is the per-autovacuum worker equivalent of the PARALLEL option of the VACUUM command. Setting this value to 0 disables parallel vacuum during autovacuum. The default is 0."]}], "signature": "WITH (autovacuum_parallel_workers = value)", "description": ["Per-table value for autovacuum_max_parallel_workers parameter. If -1 is specified, autovacuum_max_parallel_workers value will be used. If set to 0, parallel vacuum is disabled for this table. The default value is -1."]}}, "content_hash": "279a59438150f50a63da91e1848a2b76939a4ed9d94a20b9e5046f03797abd70", "imported_at": "2026-09-27T09:57:58.944", "url": "/wiki/relopts/table-autovacuum-parallel-workers/?v=18", "cells": [{"major": "10", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 10.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-autovacuum-parallel-workers/?v=10"}, {"major": "11", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 11.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-autovacuum-parallel-workers/?v=11"}, {"major": "12", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 12.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-autovacuum-parallel-workers/?v=12"}, {"major": "13", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 13.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-autovacuum-parallel-workers/?v=13"}, {"major": "14", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 14.24 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-autovacuum-parallel-workers/?v=14"}, {"major": "15", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 15.19 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-autovacuum-parallel-workers/?v=15"}, {"major": "16", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 16.15 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-autovacuum-parallel-workers/?v=16"}, {"major": "17", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 17.11 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-autovacuum-parallel-workers/?v=17"}, {"major": "18", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 18.6 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-autovacuum-parallel-workers/?v=18"}, {"major": "19", "state": "added", "label": "First recorded in this sample", "title": "PostgreSQL 19 beta 4 \u00b7 First recorded in this sample", "url": "/wiki/relopts/table-autovacuum-parallel-workers/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-parallel-workers/?v=20"}], "present": false}, {"slug": "table-autovacuum-vacuum-cost-delay", "name": "autovacuum_vacuum_cost_delay", "name_zh": "autovacuum_vacuum_cost_delay", "category": "Tables and materialized views", "summary": "Per-table value for autovacuum_vacuum_cost_delay parameter.", "aliases": ["table.autovacuum_vacuum_cost_delay"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_cost_delay/?v=10", "label": "Global parameter autovacuum_vacuum_cost_delay"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_delay", "sha256": "a8c8d51fd43c0e169a2ce6bcb094c1dbd5f0f6cd6e90cabc86f6542039600355"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_delay", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost delay value that will be used in automatic VACUUM operations. If -1 is specified, the regular vacuum_cost_delay value will be used. The default value is 20 milliseconds. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_cost_delay = value)", "description": ["Per-table value for autovacuum_vacuum_cost_delay parameter."]}, "11": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_cost_delay/?v=11", "label": "Global parameter autovacuum_vacuum_cost_delay"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_delay", "sha256": "a553adbaa0edb4dbdf216a59031edf5974a2791c02e12f3a6f23a0df0cdc59d1"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_delay", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost delay value that will be used in automatic VACUUM operations. If -1 is specified, the regular vacuum_cost_delay value will be used. The default value is 20 milliseconds. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_cost_delay = value)", "description": ["Per-table value for autovacuum_vacuum_cost_delay parameter."]}, "12": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_cost_delay/?v=12", "label": "Global parameter autovacuum_vacuum_cost_delay"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-DELAY", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_delay", "sha256": "bb486d78e8d17e633e046674781b62e0cf0f77efbb48cd6fffa5fd6b34ac98e6"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_delay", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost delay value that will be used in automatic VACUUM operations. If -1 is specified, the regular vacuum_cost_delay value will be used. If this value is specified without units, it is taken as milliseconds. The default value is 2 milliseconds. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_cost_delay = value)", "description": ["Per-table value for autovacuum_vacuum_cost_delay parameter."]}, "13": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_cost_delay/?v=13", "label": "Global parameter autovacuum_vacuum_cost_delay"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-DELAY", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_delay", "sha256": "d26d014ad3850d3dbbbc1bce41bc267205baa1523b73e48fdd9e7165b6f6785e"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_delay", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost delay value that will be used in automatic VACUUM operations. If -1 is specified, the regular vacuum_cost_delay value will be used. If this value is specified without units, it is taken as milliseconds. The default value is 2 milliseconds. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_cost_delay = value)", "description": ["Per-table value for autovacuum_vacuum_cost_delay parameter."]}, "14": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_cost_delay/?v=14", "label": "Global parameter autovacuum_vacuum_cost_delay"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-DELAY", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_delay", "sha256": "03e821969b789b688f725579aa8bd52763880e798ca8680d894f2c12861724cf"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_delay", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost delay value that will be used in automatic VACUUM operations. If -1 is specified, the regular vacuum_cost_delay value will be used. If this value is specified without units, it is taken as milliseconds. The default value is 2 milliseconds. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_cost_delay = value)", "description": ["Per-table value for autovacuum_vacuum_cost_delay parameter."]}, "15": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_cost_delay/?v=15", "label": "Global parameter autovacuum_vacuum_cost_delay"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-DELAY", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_delay", "sha256": "993bb5fe87856e4c4cb9aedac41232b5915272a65226f57e7fbf0713be2b13f4"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_delay", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost delay value that will be used in automatic VACUUM operations. If -1 is specified, the regular vacuum_cost_delay value will be used. If this value is specified without units, it is taken as milliseconds. The default value is 2 milliseconds. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_cost_delay = value)", "description": ["Per-table value for autovacuum_vacuum_cost_delay parameter."]}, "16": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_cost_delay/?v=16", "label": "Global parameter autovacuum_vacuum_cost_delay"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-DELAY", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_delay", "sha256": "b16c76b3ffb04e1e6601c44b44e2237f2a97916a52ca9b156a820abdf6545547"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_delay", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost delay value that will be used in automatic VACUUM operations. If -1 is specified, the regular vacuum_cost_delay value will be used. If this value is specified without units, it is taken as milliseconds. The default value is 2 milliseconds. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_cost_delay = value)", "description": ["Per-table value for autovacuum_vacuum_cost_delay parameter."]}, "17": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_cost_delay/?v=17", "label": "Global parameter autovacuum_vacuum_cost_delay"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-DELAY", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_delay", "sha256": "8caf714d72c9f2ed5f0f8d65041109e0ab8845c7c1169c0febef5193bdaef36d"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_delay", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost delay value that will be used in automatic VACUUM operations. If -1 is specified, the regular vacuum_cost_delay value will be used. If this value is specified without units, it is taken as milliseconds. The default value is 2 milliseconds. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_cost_delay = value)", "description": ["Per-table value for autovacuum_vacuum_cost_delay parameter."]}, "18": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_cost_delay/?v=18", "label": "Global parameter autovacuum_vacuum_cost_delay"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-DELAY", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_delay", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_delay", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost delay value that will be used in automatic VACUUM operations. If -1 is specified, the regular vacuum_cost_delay value will be used. If this value is specified without units, it is taken as milliseconds. The default value is 2 milliseconds. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_cost_delay = value)", "description": ["Per-table value for autovacuum_vacuum_cost_delay parameter."]}, "19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_cost_delay/?v=19", "label": "Global parameter autovacuum_vacuum_cost_delay"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-DELAY", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_delay", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_delay", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost delay value that will be used in automatic VACUUM operations. If -1 is specified, the regular vacuum_cost_delay value will be used. If this value is specified without units, it is taken as milliseconds. The default value is 2 milliseconds. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_cost_delay = value)", "description": ["Per-table value for autovacuum_vacuum_cost_delay parameter."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_cost_delay/?v=20", "label": "Global parameter autovacuum_vacuum_cost_delay"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-DELAY", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_delay", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_delay", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost delay value that will be used in automatic VACUUM operations. If -1 is specified, the regular vacuum_cost_delay value will be used. If this value is specified without units, it is taken as milliseconds. The default value is 2 milliseconds. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_cost_delay = value)", "description": ["Per-table value for autovacuum_vacuum_cost_delay parameter."]}}, "content_hash": "0af192487d373910cff669f24fa7200d5bcc4372edbc9fbe5ed33887b12ffa50", "imported_at": "2026-09-27T09:57:58.945", "url": "/wiki/relopts/table-autovacuum-vacuum-cost-delay/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-cost-delay/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-cost-delay/?v=11"}, {"major": "12", "state": "changed", "label": "Interface or attribute change", "title": "PostgreSQL 12.22 \u00b7 Interface or attribute change", "url": "/wiki/relopts/table-autovacuum-vacuum-cost-delay/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-cost-delay/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-cost-delay/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-cost-delay/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-cost-delay/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-cost-delay/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-cost-delay/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-cost-delay/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-cost-delay/?v=20"}], "present": true}, {"slug": "table-autovacuum-vacuum-cost-limit", "name": "autovacuum_vacuum_cost_limit", "name_zh": "autovacuum_vacuum_cost_limit", "category": "Tables and materialized views", "summary": "Per-table value for autovacuum_vacuum_cost_limit parameter.", "aliases": ["table.autovacuum_vacuum_cost_limit"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_cost_limit/?v=10", "label": "Global parameter autovacuum_vacuum_cost_limit"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_limit", "sha256": "a8c8d51fd43c0e169a2ce6bcb094c1dbd5f0f6cd6e90cabc86f6542039600355"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost limit value that will be used in automatic VACUUM operations. If -1 is specified (which is the default), the regular vacuum_cost_limit value will be used. Note that the value is distributed proportionally among the running autovacuum workers, if there is more than one, so that the sum of the limits for each worker does not exceed the value of this variable. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_cost_limit = value)", "description": ["Per-table value for autovacuum_vacuum_cost_limit parameter."]}, "11": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_cost_limit/?v=11", "label": "Global parameter autovacuum_vacuum_cost_limit"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_limit", "sha256": "a553adbaa0edb4dbdf216a59031edf5974a2791c02e12f3a6f23a0df0cdc59d1"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost limit value that will be used in automatic VACUUM operations. If -1 is specified (which is the default), the regular vacuum_cost_limit value will be used. Note that the value is distributed proportionally among the running autovacuum workers, if there is more than one, so that the sum of the limits for each worker does not exceed the value of this variable. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_cost_limit = value)", "description": ["Per-table value for autovacuum_vacuum_cost_limit parameter."]}, "12": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_cost_limit/?v=12", "label": "Global parameter autovacuum_vacuum_cost_limit"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_limit", "sha256": "bb486d78e8d17e633e046674781b62e0cf0f77efbb48cd6fffa5fd6b34ac98e6"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost limit value that will be used in automatic VACUUM operations. If -1 is specified (which is the default), the regular vacuum_cost_limit value will be used. Note that the value is distributed proportionally among the running autovacuum workers, if there is more than one, so that the sum of the limits for each worker does not exceed the value of this variable. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_cost_limit = value)", "description": ["Per-table value for autovacuum_vacuum_cost_limit parameter."]}, "13": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_cost_limit/?v=13", "label": "Global parameter autovacuum_vacuum_cost_limit"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_limit", "sha256": "d26d014ad3850d3dbbbc1bce41bc267205baa1523b73e48fdd9e7165b6f6785e"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost limit value that will be used in automatic VACUUM operations. If -1 is specified (which is the default), the regular vacuum_cost_limit value will be used. Note that the value is distributed proportionally among the running autovacuum workers, if there is more than one, so that the sum of the limits for each worker does not exceed the value of this variable. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_cost_limit = value)", "description": ["Per-table value for autovacuum_vacuum_cost_limit parameter."]}, "14": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_cost_limit/?v=14", "label": "Global parameter autovacuum_vacuum_cost_limit"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_limit", "sha256": "03e821969b789b688f725579aa8bd52763880e798ca8680d894f2c12861724cf"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost limit value that will be used in automatic VACUUM operations. If -1 is specified (which is the default), the regular vacuum_cost_limit value will be used. Note that the value is distributed proportionally among the running autovacuum workers, if there is more than one, so that the sum of the limits for each worker does not exceed the value of this variable. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_cost_limit = value)", "description": ["Per-table value for autovacuum_vacuum_cost_limit parameter."]}, "15": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_cost_limit/?v=15", "label": "Global parameter autovacuum_vacuum_cost_limit"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_limit", "sha256": "993bb5fe87856e4c4cb9aedac41232b5915272a65226f57e7fbf0713be2b13f4"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost limit value that will be used in automatic VACUUM operations. If -1 is specified (which is the default), the regular vacuum_cost_limit value will be used. Note that the value is distributed proportionally among the running autovacuum workers, if there is more than one, so that the sum of the limits for each worker does not exceed the value of this variable. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_cost_limit = value)", "description": ["Per-table value for autovacuum_vacuum_cost_limit parameter."]}, "16": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_cost_limit/?v=16", "label": "Global parameter autovacuum_vacuum_cost_limit"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_limit", "sha256": "b16c76b3ffb04e1e6601c44b44e2237f2a97916a52ca9b156a820abdf6545547"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost limit value that will be used in automatic VACUUM operations. If -1 is specified (which is the default), the regular vacuum_cost_limit value will be used. Note that the value is distributed proportionally among the running autovacuum workers, if there is more than one, so that the sum of the limits for each worker does not exceed the value of this variable. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_cost_limit = value)", "description": ["Per-table value for autovacuum_vacuum_cost_limit parameter."]}, "17": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_cost_limit/?v=17", "label": "Global parameter autovacuum_vacuum_cost_limit"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_limit", "sha256": "8caf714d72c9f2ed5f0f8d65041109e0ab8845c7c1169c0febef5193bdaef36d"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost limit value that will be used in automatic VACUUM operations. If -1 is specified (which is the default), the regular vacuum_cost_limit value will be used. Note that the value is distributed proportionally among the running autovacuum workers, if there is more than one, so that the sum of the limits for each worker does not exceed the value of this variable. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_cost_limit = value)", "description": ["Per-table value for autovacuum_vacuum_cost_limit parameter."]}, "18": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_cost_limit/?v=18", "label": "Global parameter autovacuum_vacuum_cost_limit"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_limit", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost limit value that will be used in automatic VACUUM operations. If -1 is specified (which is the default), the regular vacuum_cost_limit value will be used. Note that the value is distributed proportionally among the running autovacuum workers, if there is more than one, so that the sum of the limits for each worker does not exceed the value of this variable. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_cost_limit = value)", "description": ["Per-table value for autovacuum_vacuum_cost_limit parameter."]}, "19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_cost_limit/?v=19", "label": "Global parameter autovacuum_vacuum_cost_limit"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_limit", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost limit value that will be used in automatic VACUUM operations. If -1 is specified (which is the default), the regular vacuum_cost_limit value will be used. Note that the value is distributed proportionally among the running autovacuum workers, if there is more than one, so that the sum of the limits for each worker does not exceed the value of this variable. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_cost_limit = value)", "description": ["Per-table value for autovacuum_vacuum_cost_limit parameter."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_cost_limit/?v=20", "label": "Global parameter autovacuum_vacuum_cost_limit"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_cost_limit", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_cost_limit", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the cost limit value that will be used in automatic VACUUM operations. If -1 is specified (which is the default), the regular vacuum_cost_limit value will be used. Note that the value is distributed proportionally among the running autovacuum workers, if there is more than one, so that the sum of the limits for each worker does not exceed the value of this variable. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_cost_limit = value)", "description": ["Per-table value for autovacuum_vacuum_cost_limit parameter."]}}, "content_hash": "1d7b5ee77dfa18a443e9f41e844ea01bbd4a7cac5ca54c5c0f670eac0437bb91", "imported_at": "2026-09-27T09:57:58.947", "url": "/wiki/relopts/table-autovacuum-vacuum-cost-limit/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-cost-limit/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-cost-limit/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-cost-limit/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-cost-limit/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-cost-limit/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-cost-limit/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-cost-limit/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-cost-limit/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-cost-limit/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-cost-limit/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-cost-limit/?v=20"}], "present": true}, {"slug": "table-autovacuum-vacuum-insert-scale-factor", "name": "autovacuum_vacuum_insert_scale_factor", "name_zh": "autovacuum_vacuum_insert_scale_factor", "category": "Tables and materialized views", "summary": "Per-table value for autovacuum_vacuum_insert_scale_factor parameter.", "aliases": ["table.autovacuum_vacuum_insert_scale_factor"], "versions": {"13": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_insert_scale_factor/?v=13", "label": "Global parameter autovacuum_vacuum_insert_scale_factor"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "sha256": "d26d014ad3850d3dbbbc1bce41bc267205baa1523b73e48fdd9e7165b6f6785e"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_insert_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_insert_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_insert_scale_factor parameter."]}, "14": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_insert_scale_factor/?v=14", "label": "Global parameter autovacuum_vacuum_insert_scale_factor"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "sha256": "03e821969b789b688f725579aa8bd52763880e798ca8680d894f2c12861724cf"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_insert_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_insert_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_insert_scale_factor parameter."]}, "15": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_insert_scale_factor/?v=15", "label": "Global parameter autovacuum_vacuum_insert_scale_factor"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "sha256": "993bb5fe87856e4c4cb9aedac41232b5915272a65226f57e7fbf0713be2b13f4"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_insert_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_insert_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_insert_scale_factor parameter."]}, "16": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_insert_scale_factor/?v=16", "label": "Global parameter autovacuum_vacuum_insert_scale_factor"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "sha256": "b16c76b3ffb04e1e6601c44b44e2237f2a97916a52ca9b156a820abdf6545547"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_insert_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_insert_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_insert_scale_factor parameter."]}, "17": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_insert_scale_factor/?v=17", "label": "Global parameter autovacuum_vacuum_insert_scale_factor"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "sha256": "8caf714d72c9f2ed5f0f8d65041109e0ab8845c7c1169c0febef5193bdaef36d"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_insert_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_insert_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_insert_scale_factor parameter."]}, "18": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_insert_scale_factor/?v=18", "label": "Global parameter autovacuum_vacuum_insert_scale_factor"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the unfrozen pages in the table to add to autovacuum_vacuum_insert_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of unfrozen pages in table). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_insert_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_insert_scale_factor parameter."]}, "19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_insert_scale_factor/?v=19", "label": "Global parameter autovacuum_vacuum_insert_scale_factor"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the unfrozen pages in the table to add to autovacuum_vacuum_insert_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of unfrozen pages in table). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_insert_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_insert_scale_factor parameter."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_insert_scale_factor/?v=20", "label": "Global parameter autovacuum_vacuum_insert_scale_factor"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-SCALE-FACTOR", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the unfrozen pages in the table to add to autovacuum_vacuum_insert_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of unfrozen pages in table). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_insert_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_insert_scale_factor parameter."]}}, "content_hash": "3135c4656037ad2f804b6f9bcfad7fe9add4df4c0f85aa35ec2e6348ac44b120", "imported_at": "2026-09-27T09:57:58.949", "url": "/wiki/relopts/table-autovacuum-vacuum-insert-scale-factor/?v=18", "cells": [{"major": "10", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 10.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-autovacuum-vacuum-insert-scale-factor/?v=10"}, {"major": "11", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 11.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-autovacuum-vacuum-insert-scale-factor/?v=11"}, {"major": "12", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 12.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-autovacuum-vacuum-insert-scale-factor/?v=12"}, {"major": "13", "state": "added", "label": "First recorded in this sample", "title": "PostgreSQL 13.23 \u00b7 First recorded in this sample", "url": "/wiki/relopts/table-autovacuum-vacuum-insert-scale-factor/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-insert-scale-factor/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-insert-scale-factor/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-insert-scale-factor/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-insert-scale-factor/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-insert-scale-factor/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-insert-scale-factor/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-insert-scale-factor/?v=20"}], "present": true}, {"slug": "table-autovacuum-vacuum-insert-threshold", "name": "autovacuum_vacuum_insert_threshold", "name_zh": "autovacuum_vacuum_insert_threshold", "category": "Tables and materialized views", "summary": "Per-table value for autovacuum_vacuum_insert_threshold parameter. The special value of -1 may be used to disable insert vacuums on the table.", "aliases": ["table.autovacuum_vacuum_insert_threshold"], "versions": {"13": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_insert_threshold/?v=13", "label": "Global parameter autovacuum_vacuum_insert_threshold"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_threshold", "sha256": "d26d014ad3850d3dbbbc1bce41bc267205baa1523b73e48fdd9e7165b6f6785e"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the number of inserted tuples needed to trigger a VACUUM in any one table. The default is 1000 tuples. If -1 is specified, autovacuum will not trigger a VACUUM operation on any tables based on the number of inserts. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_insert_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_insert_threshold parameter. The special value of -1 may be used to disable insert vacuums on the table."]}, "14": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_insert_threshold/?v=14", "label": "Global parameter autovacuum_vacuum_insert_threshold"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_threshold", "sha256": "03e821969b789b688f725579aa8bd52763880e798ca8680d894f2c12861724cf"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the number of inserted tuples needed to trigger a VACUUM in any one table. The default is 1000 tuples. If -1 is specified, autovacuum will not trigger a VACUUM operation on any tables based on the number of inserts. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_insert_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_insert_threshold parameter. The special value of -1 may be used to disable insert vacuums on the table."]}, "15": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_insert_threshold/?v=15", "label": "Global parameter autovacuum_vacuum_insert_threshold"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_threshold", "sha256": "993bb5fe87856e4c4cb9aedac41232b5915272a65226f57e7fbf0713be2b13f4"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the number of inserted tuples needed to trigger a VACUUM in any one table. The default is 1000 tuples. If -1 is specified, autovacuum will not trigger a VACUUM operation on any tables based on the number of inserts. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_insert_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_insert_threshold parameter. The special value of -1 may be used to disable insert vacuums on the table."]}, "16": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_insert_threshold/?v=16", "label": "Global parameter autovacuum_vacuum_insert_threshold"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_threshold", "sha256": "b16c76b3ffb04e1e6601c44b44e2237f2a97916a52ca9b156a820abdf6545547"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the number of inserted tuples needed to trigger a VACUUM in any one table. The default is 1000 tuples. If -1 is specified, autovacuum will not trigger a VACUUM operation on any tables based on the number of inserts. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_insert_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_insert_threshold parameter. The special value of -1 may be used to disable insert vacuums on the table."]}, "17": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_insert_threshold/?v=17", "label": "Global parameter autovacuum_vacuum_insert_threshold"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_threshold", "sha256": "8caf714d72c9f2ed5f0f8d65041109e0ab8845c7c1169c0febef5193bdaef36d"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the number of inserted tuples needed to trigger a VACUUM in any one table. The default is 1000 tuples. If -1 is specified, autovacuum will not trigger a VACUUM operation on any tables based on the number of inserts. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_insert_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_insert_threshold parameter. The special value of -1 may be used to disable insert vacuums on the table."]}, "18": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_insert_threshold/?v=18", "label": "Global parameter autovacuum_vacuum_insert_threshold"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_threshold", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the number of inserted tuples needed to trigger a VACUUM in any one table. The default is 1000 tuples. If -1 is specified, autovacuum will not trigger a VACUUM operation on any tables based on the number of inserts. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_insert_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_insert_threshold parameter. The special value of -1 may be used to disable insert vacuums on the table."]}, "19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_insert_threshold/?v=19", "label": "Global parameter autovacuum_vacuum_insert_threshold"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_threshold", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the number of inserted tuples needed to trigger a VACUUM in any one table. The default is 1000 tuples. If -1 is specified, autovacuum will not trigger a VACUUM operation on any tables based on the number of inserts. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_insert_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_insert_threshold parameter. The special value of -1 may be used to disable insert vacuums on the table."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_insert_threshold/?v=20", "label": "Global parameter autovacuum_vacuum_insert_threshold"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-INSERT-THRESHOLD", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_insert_threshold", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_insert_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the number of inserted tuples needed to trigger a VACUUM in any one table. The default is 1000 tuples. If -1 is specified, autovacuum will not trigger a VACUUM operation on any tables based on the number of inserts. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_insert_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_insert_threshold parameter. The special value of -1 may be used to disable insert vacuums on the table."]}}, "content_hash": "5788d02a257df599b6c78b27f9909964c16f781abd9c0654e7946e8d60d41263", "imported_at": "2026-09-27T09:57:58.951", "url": "/wiki/relopts/table-autovacuum-vacuum-insert-threshold/?v=18", "cells": [{"major": "10", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 10.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-autovacuum-vacuum-insert-threshold/?v=10"}, {"major": "11", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 11.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-autovacuum-vacuum-insert-threshold/?v=11"}, {"major": "12", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 12.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-autovacuum-vacuum-insert-threshold/?v=12"}, {"major": "13", "state": "added", "label": "First recorded in this sample", "title": "PostgreSQL 13.23 \u00b7 First recorded in this sample", "url": "/wiki/relopts/table-autovacuum-vacuum-insert-threshold/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-insert-threshold/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-insert-threshold/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-insert-threshold/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-insert-threshold/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-insert-threshold/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-insert-threshold/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-insert-threshold/?v=20"}], "present": true}, {"slug": "table-autovacuum-vacuum-max-threshold", "name": "autovacuum_vacuum_max_threshold", "name_zh": "autovacuum_vacuum_max_threshold", "category": "Tables and materialized views", "summary": "Per-table value for autovacuum_vacuum_max_threshold parameter.", "aliases": ["table.autovacuum_vacuum_max_threshold"], "versions": {"18": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_max_threshold/?v=18", "label": "Global parameter autovacuum_vacuum_max_threshold"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-MAX-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-MAX-THRESHOLD", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_max_threshold", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_max_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum number of updated or deleted tuples needed to trigger a VACUUM in any one table, i.e., a limit on the value calculated with autovacuum_vacuum_threshold and autovacuum_vacuum_scale_factor . The default is 100,000,000 tuples. If -1 is specified, autovacuum will not enforce a maximum number of updated or deleted tuples that will trigger a VACUUM operation. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing storage parameters."]}], "signature": "WITH (autovacuum_vacuum_max_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_max_threshold parameter."]}, "19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_max_threshold/?v=19", "label": "Global parameter autovacuum_vacuum_max_threshold"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-MAX-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-MAX-THRESHOLD", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_max_threshold", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_max_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum number of updated or deleted tuples needed to trigger a VACUUM in any one table, i.e., a limit on the value calculated with autovacuum_vacuum_threshold and autovacuum_vacuum_scale_factor . The default is 100,000,000 tuples. If -1 is specified, autovacuum will not enforce a maximum number of updated or deleted tuples that will trigger a VACUUM operation. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing storage parameters."]}], "signature": "WITH (autovacuum_vacuum_max_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_max_threshold parameter."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_max_threshold/?v=20", "label": "Global parameter autovacuum_vacuum_max_threshold"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-MAX-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-MAX-THRESHOLD", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_max_threshold", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_max_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum number of updated or deleted tuples needed to trigger a VACUUM in any one table, i.e., a limit on the value calculated with autovacuum_vacuum_threshold and autovacuum_vacuum_scale_factor . The default is 100,000,000 tuples. If -1 is specified, autovacuum will not enforce a maximum number of updated or deleted tuples that will trigger a VACUUM operation. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing storage parameters."]}], "signature": "WITH (autovacuum_vacuum_max_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_max_threshold parameter."]}}, "content_hash": "4b1ee46dc1d050efacc47e89953bb524ed785877bd56dcf5f193491905e7cc75", "imported_at": "2026-09-27T09:57:58.953", "url": "/wiki/relopts/table-autovacuum-vacuum-max-threshold/?v=18", "cells": [{"major": "10", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 10.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-autovacuum-vacuum-max-threshold/?v=10"}, {"major": "11", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 11.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-autovacuum-vacuum-max-threshold/?v=11"}, {"major": "12", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 12.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-autovacuum-vacuum-max-threshold/?v=12"}, {"major": "13", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 13.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-autovacuum-vacuum-max-threshold/?v=13"}, {"major": "14", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 14.24 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-autovacuum-vacuum-max-threshold/?v=14"}, {"major": "15", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 15.19 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-autovacuum-vacuum-max-threshold/?v=15"}, {"major": "16", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 16.15 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-autovacuum-vacuum-max-threshold/?v=16"}, {"major": "17", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 17.11 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-autovacuum-vacuum-max-threshold/?v=17"}, {"major": "18", "state": "added", "label": "First recorded in this sample", "title": "PostgreSQL 18.6 \u00b7 First recorded in this sample", "url": "/wiki/relopts/table-autovacuum-vacuum-max-threshold/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-max-threshold/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-max-threshold/?v=20"}], "present": true}, {"slug": "table-autovacuum-vacuum-scale-factor", "name": "autovacuum_vacuum_scale_factor", "name_zh": "autovacuum_vacuum_scale_factor", "category": "Tables and materialized views", "summary": "Per-table value for autovacuum_vacuum_scale_factor parameter.", "aliases": ["table.autovacuum_vacuum_scale_factor"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_scale_factor/?v=10", "label": "Global parameter autovacuum_vacuum_scale_factor"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_scale_factor", "sha256": "a8c8d51fd43c0e169a2ce6bcb094c1dbd5f0f6cd6e90cabc86f6542039600355"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_scale_factor parameter."]}, "11": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_scale_factor/?v=11", "label": "Global parameter autovacuum_vacuum_scale_factor"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_scale_factor", "sha256": "a553adbaa0edb4dbdf216a59031edf5974a2791c02e12f3a6f23a0df0cdc59d1"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_scale_factor parameter."]}, "12": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_scale_factor/?v=12", "label": "Global parameter autovacuum_vacuum_scale_factor"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_scale_factor", "sha256": "bb486d78e8d17e633e046674781b62e0cf0f77efbb48cd6fffa5fd6b34ac98e6"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_scale_factor parameter."]}, "13": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_scale_factor/?v=13", "label": "Global parameter autovacuum_vacuum_scale_factor"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_scale_factor", "sha256": "d26d014ad3850d3dbbbc1bce41bc267205baa1523b73e48fdd9e7165b6f6785e"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_scale_factor parameter."]}, "14": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_scale_factor/?v=14", "label": "Global parameter autovacuum_vacuum_scale_factor"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_scale_factor", "sha256": "03e821969b789b688f725579aa8bd52763880e798ca8680d894f2c12861724cf"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_scale_factor parameter."]}, "15": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_scale_factor/?v=15", "label": "Global parameter autovacuum_vacuum_scale_factor"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_scale_factor", "sha256": "993bb5fe87856e4c4cb9aedac41232b5915272a65226f57e7fbf0713be2b13f4"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_scale_factor parameter."]}, "16": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_scale_factor/?v=16", "label": "Global parameter autovacuum_vacuum_scale_factor"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_scale_factor", "sha256": "b16c76b3ffb04e1e6601c44b44e2237f2a97916a52ca9b156a820abdf6545547"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_scale_factor parameter."]}, "17": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_scale_factor/?v=17", "label": "Global parameter autovacuum_vacuum_scale_factor"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_scale_factor", "sha256": "8caf714d72c9f2ed5f0f8d65041109e0ab8845c7c1169c0febef5193bdaef36d"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_scale_factor parameter."]}, "18": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_scale_factor/?v=18", "label": "Global parameter autovacuum_vacuum_scale_factor"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_scale_factor", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_scale_factor parameter."]}, "19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_scale_factor/?v=19", "label": "Global parameter autovacuum_vacuum_scale_factor"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_scale_factor", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_scale_factor parameter."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_scale_factor/?v=20", "label": "Global parameter autovacuum_vacuum_scale_factor"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-SCALE-FACTOR", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_scale_factor", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_scale_factor", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies a fraction of the table size to add to autovacuum_vacuum_threshold when deciding whether to trigger a VACUUM . The default is 0.2 (20% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_scale_factor = value)", "description": ["Per-table value for autovacuum_vacuum_scale_factor parameter."]}}, "content_hash": "6fcd2409ee34521d495297c88b706dc755e234cc4749218c8b1772f9d04c246f", "imported_at": "2026-09-27T09:57:58.955", "url": "/wiki/relopts/table-autovacuum-vacuum-scale-factor/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-scale-factor/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-scale-factor/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-scale-factor/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-scale-factor/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-scale-factor/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-scale-factor/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-scale-factor/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-scale-factor/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-scale-factor/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-scale-factor/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-scale-factor/?v=20"}], "present": true}, {"slug": "table-autovacuum-vacuum-threshold", "name": "autovacuum_vacuum_threshold", "name_zh": "autovacuum_vacuum_threshold", "category": "Tables and materialized views", "summary": "Per-table value for autovacuum_vacuum_threshold parameter.", "aliases": ["table.autovacuum_vacuum_threshold"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_threshold/?v=10", "label": "Global parameter autovacuum_vacuum_threshold"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_threshold", "sha256": "a8c8d51fd43c0e169a2ce6bcb094c1dbd5f0f6cd6e90cabc86f6542039600355"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of updated or deleted tuples needed to trigger a VACUUM in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_threshold parameter."]}, "11": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_threshold/?v=11", "label": "Global parameter autovacuum_vacuum_threshold"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_threshold", "sha256": "a553adbaa0edb4dbdf216a59031edf5974a2791c02e12f3a6f23a0df0cdc59d1"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of updated or deleted tuples needed to trigger a VACUUM in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_threshold parameter."]}, "12": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_threshold/?v=12", "label": "Global parameter autovacuum_vacuum_threshold"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_threshold", "sha256": "bb486d78e8d17e633e046674781b62e0cf0f77efbb48cd6fffa5fd6b34ac98e6"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of updated or deleted tuples needed to trigger a VACUUM in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_threshold parameter."]}, "13": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_threshold/?v=13", "label": "Global parameter autovacuum_vacuum_threshold"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_threshold", "sha256": "d26d014ad3850d3dbbbc1bce41bc267205baa1523b73e48fdd9e7165b6f6785e"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of updated or deleted tuples needed to trigger a VACUUM in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_threshold parameter."]}, "14": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_threshold/?v=14", "label": "Global parameter autovacuum_vacuum_threshold"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_threshold", "sha256": "03e821969b789b688f725579aa8bd52763880e798ca8680d894f2c12861724cf"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of updated or deleted tuples needed to trigger a VACUUM in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_threshold parameter."]}, "15": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_threshold/?v=15", "label": "Global parameter autovacuum_vacuum_threshold"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_threshold", "sha256": "993bb5fe87856e4c4cb9aedac41232b5915272a65226f57e7fbf0713be2b13f4"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of updated or deleted tuples needed to trigger a VACUUM in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_threshold parameter."]}, "16": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_threshold/?v=16", "label": "Global parameter autovacuum_vacuum_threshold"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_threshold", "sha256": "b16c76b3ffb04e1e6601c44b44e2237f2a97916a52ca9b156a820abdf6545547"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of updated or deleted tuples needed to trigger a VACUUM in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_threshold parameter."]}, "17": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_threshold/?v=17", "label": "Global parameter autovacuum_vacuum_threshold"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-THRESHOLD", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: autovacuum_vacuum_threshold", "sha256": "8caf714d72c9f2ed5f0f8d65041109e0ab8845c7c1169c0febef5193bdaef36d"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of updated or deleted tuples needed to trigger a VACUUM in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_threshold parameter."]}, "18": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_threshold/?v=18", "label": "Global parameter autovacuum_vacuum_threshold"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-THRESHOLD", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_threshold", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of updated or deleted tuples needed to trigger a VACUUM in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_threshold parameter."]}, "19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_threshold/?v=19", "label": "Global parameter autovacuum_vacuum_threshold"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-THRESHOLD", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_threshold", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of updated or deleted tuples needed to trigger a VACUUM in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_threshold parameter."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/autovacuum_vacuum_threshold/?v=20", "label": "Global parameter autovacuum_vacuum_threshold"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-THRESHOLD", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-THRESHOLD", "path": "runtime-config-vacuum.html", "label": "Related global parameter: autovacuum_vacuum_threshold", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: autovacuum_vacuum_threshold", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the minimum number of updated or deleted tuples needed to trigger a VACUUM in any one table. The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (autovacuum_vacuum_threshold = value)", "description": ["Per-table value for autovacuum_vacuum_threshold parameter."]}}, "content_hash": "e998b0dbfd8e5793a05c926314923e724294c760e57f96d0d319e30faebe863a", "imported_at": "2026-09-27T09:57:58.957", "url": "/wiki/relopts/table-autovacuum-vacuum-threshold/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-threshold/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-threshold/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-threshold/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-threshold/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-threshold/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-threshold/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-threshold/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-threshold/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-threshold/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-threshold/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-autovacuum-vacuum-threshold/?v=20"}], "present": true}, {"slug": "table-fillfactor", "name": "fillfactor", "name_zh": "Tables and materialized views fillfactor", "category": "Tables and materialized views", "summary": "The fillfactor for a table is a percentage between 10 and 100. 100 (complete packing) is the default. When a smaller fillfactor is specified, INSERT operations pack table pages only to the indicated percentage; the remaining space on each page is reserved for updating rows on that page. This gives UPDATE a chance to place the updated copy of a row on the same page as the original, which is more efficient than placing it on a different page, and makes heap-only tuple updates more likely. For a table whose entries are never updated, complete packing is the best choice, but in heavily updated tables smaller fillfactors are appropriate. This parameter cannot be set for TOAST tables.", "aliases": ["table.fillfactor"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "100"}, {"label": "Range", "value": "10\u2013100 percent"}], "related": [{"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for a table is a percentage between 10 and 100. 100 (complete packing) is the default. When a smaller fillfactor is specified, INSERT operations pack table pages only to the indicated percentage; the remaining space on each page is reserved for updating rows on that page. This gives UPDATE a chance to place the updated copy of a row on the same page as the original, which is more efficient than placing it on a different page. For a table whose entries are never updated, complete packing is the best choice, but in heavily updated tables smaller fillfactors are appropriate. This parameter cannot be set for TOAST tables."]}, "11": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "100"}, {"label": "Range", "value": "10\u2013100 percent"}], "related": [{"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for a table is a percentage between 10 and 100. 100 (complete packing) is the default. When a smaller fillfactor is specified, INSERT operations pack table pages only to the indicated percentage; the remaining space on each page is reserved for updating rows on that page. This gives UPDATE a chance to place the updated copy of a row on the same page as the original, which is more efficient than placing it on a different page, and makes heap-only tuple updates more likely. For a table whose entries are never updated, complete packing is the best choice, but in heavily updated tables smaller fillfactors are appropriate. This parameter cannot be set for TOAST tables."]}, "12": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "100"}, {"label": "Range", "value": "10\u2013100 percent"}], "related": [{"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-FILLFACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for a table is a percentage between 10 and 100. 100 (complete packing) is the default. When a smaller fillfactor is specified, INSERT operations pack table pages only to the indicated percentage; the remaining space on each page is reserved for updating rows on that page. This gives UPDATE a chance to place the updated copy of a row on the same page as the original, which is more efficient than placing it on a different page, and makes heap-only tuple updates more likely. For a table whose entries are never updated, complete packing is the best choice, but in heavily updated tables smaller fillfactors are appropriate. This parameter cannot be set for TOAST tables."]}, "13": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "100"}, {"label": "Range", "value": "10\u2013100 percent"}], "related": [{"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-FILLFACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for a table is a percentage between 10 and 100. 100 (complete packing) is the default. When a smaller fillfactor is specified, INSERT operations pack table pages only to the indicated percentage; the remaining space on each page is reserved for updating rows on that page. This gives UPDATE a chance to place the updated copy of a row on the same page as the original, which is more efficient than placing it on a different page, and makes heap-only tuple updates more likely. For a table whose entries are never updated, complete packing is the best choice, but in heavily updated tables smaller fillfactors are appropriate. This parameter cannot be set for TOAST tables."]}, "14": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "100"}, {"label": "Range", "value": "10\u2013100 percent"}], "related": [{"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-FILLFACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for a table is a percentage between 10 and 100. 100 (complete packing) is the default. When a smaller fillfactor is specified, INSERT operations pack table pages only to the indicated percentage; the remaining space on each page is reserved for updating rows on that page. This gives UPDATE a chance to place the updated copy of a row on the same page as the original, which is more efficient than placing it on a different page, and makes heap-only tuple updates more likely. For a table whose entries are never updated, complete packing is the best choice, but in heavily updated tables smaller fillfactors are appropriate. This parameter cannot be set for TOAST tables."]}, "15": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "100"}, {"label": "Range", "value": "10\u2013100 percent"}], "related": [{"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-FILLFACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for a table is a percentage between 10 and 100. 100 (complete packing) is the default. When a smaller fillfactor is specified, INSERT operations pack table pages only to the indicated percentage; the remaining space on each page is reserved for updating rows on that page. This gives UPDATE a chance to place the updated copy of a row on the same page as the original, which is more efficient than placing it on a different page, and makes heap-only tuple updates more likely. For a table whose entries are never updated, complete packing is the best choice, but in heavily updated tables smaller fillfactors are appropriate. This parameter cannot be set for TOAST tables."]}, "16": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "100"}, {"label": "Range", "value": "10\u2013100 percent"}], "related": [{"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-FILLFACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for a table is a percentage between 10 and 100. 100 (complete packing) is the default. When a smaller fillfactor is specified, INSERT operations pack table pages only to the indicated percentage; the remaining space on each page is reserved for updating rows on that page. This gives UPDATE a chance to place the updated copy of a row on the same page as the original, which is more efficient than placing it on a different page, and makes heap-only tuple updates more likely. For a table whose entries are never updated, complete packing is the best choice, but in heavily updated tables smaller fillfactors are appropriate. This parameter cannot be set for TOAST tables."]}, "17": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "100"}, {"label": "Range", "value": "10\u2013100 percent"}], "related": [{"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-FILLFACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for a table is a percentage between 10 and 100. 100 (complete packing) is the default. When a smaller fillfactor is specified, INSERT operations pack table pages only to the indicated percentage; the remaining space on each page is reserved for updating rows on that page. This gives UPDATE a chance to place the updated copy of a row on the same page as the original, which is more efficient than placing it on a different page, and makes heap-only tuple updates more likely. For a table whose entries are never updated, complete packing is the best choice, but in heavily updated tables smaller fillfactors are appropriate. This parameter cannot be set for TOAST tables."]}, "18": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "100"}, {"label": "Range", "value": "10\u2013100 percent"}], "related": [{"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-FILLFACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for a table is a percentage between 10 and 100. 100 (complete packing) is the default. When a smaller fillfactor is specified, INSERT operations pack table pages only to the indicated percentage; the remaining space on each page is reserved for updating rows on that page. This gives UPDATE a chance to place the updated copy of a row on the same page as the original, which is more efficient than placing it on a different page, and makes heap-only tuple updates more likely. For a table whose entries are never updated, complete packing is the best choice, but in heavily updated tables smaller fillfactors are appropriate. This parameter cannot be set for TOAST tables."]}, "19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "100"}, {"label": "Range", "value": "10\u2013100 percent"}], "related": [{"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-FILLFACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for a table is a percentage between 10 and 100. 100 (complete packing) is the default. When a smaller fillfactor is specified, INSERT operations pack table pages only to the indicated percentage; the remaining space on each page is reserved for updating rows on that page. This gives UPDATE a chance to place the updated copy of a row on the same page as the original, which is more efficient than placing it on a different page, and makes heap-only tuple updates more likely. For a table whose entries are never updated, complete packing is the best choice, but in heavily updated tables smaller fillfactors are appropriate. This parameter cannot be set for TOAST tables."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}, {"label": "Default", "value": "100"}, {"label": "Range", "value": "10\u2013100 percent"}], "related": [{"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-FILLFACTOR", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (fillfactor = value)", "description": ["The fillfactor for a table is a percentage between 10 and 100. 100 (complete packing) is the default. When a smaller fillfactor is specified, INSERT operations pack table pages only to the indicated percentage; the remaining space on each page is reserved for updating rows on that page. This gives UPDATE a chance to place the updated copy of a row on the same page as the original, which is more efficient than placing it on a different page, and makes heap-only tuple updates more likely. For a table whose entries are never updated, complete packing is the best choice, but in heavily updated tables smaller fillfactors are appropriate. This parameter cannot be set for TOAST tables."]}}, "content_hash": "cabfedbbeb8e859b2e0122a29f11e1baf6b88ed75541ac79d84688b46c9417ff", "imported_at": "2026-09-27T09:57:58.959", "url": "/wiki/relopts/table-fillfactor/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/table-fillfactor/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/table-fillfactor/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/table-fillfactor/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/table-fillfactor/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/table-fillfactor/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/table-fillfactor/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/table-fillfactor/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/table-fillfactor/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/table-fillfactor/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-fillfactor/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-fillfactor/?v=20"}], "present": true}, {"slug": "table-log-autoanalyze-min-duration", "name": "log_autoanalyze_min_duration", "name_zh": "log_autoanalyze_min_duration", "category": "Tables and materialized views", "summary": "Not recorded in the selected version.", "aliases": ["table.log_autoanalyze_min_duration"], "versions": {"19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/log_autoanalyze_min_duration/?v=19", "label": "Global parameter log_autoanalyze_min_duration"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-LOG-AUTOANALYZE-MIN-DURATION", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-logging.html#GUC-LOG-AUTOANALYZE-MIN-DURATION", "path": "runtime-config-logging.html", "label": "Related global parameter: log_autoanalyze_min_duration", "sha256": "6bc8c26ccff0749f936162b21d68912f6be287148245e296d602589f7782a116"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: log_autoanalyze_min_duration", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Causes analyze action executed by autovacuum to be logged if it ran for at least the specified amount of time. Setting this to zero logs all analyze actions by autovacuum. -1 disables logging analyze actions by autovacuum. If this value is specified without units, it is taken as milliseconds. For example, if you set this to 250ms then all automatic analyzes that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1 , a message will be logged if an analyze action by autovacuum is skipped due to a conflicting lock or a concurrently dropped relation. The default is 10min . Enabling this parameter can be helpful in tracking analyze activity by autovacuum. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (log_autoanalyze_min_duration = value)", "description": ["Per-table value for log_autoanalyze_min_duration parameter."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/log_autoanalyze_min_duration/?v=20", "label": "Global parameter log_autoanalyze_min_duration"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-LOG-AUTOANALYZE-MIN-DURATION", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-logging.html#GUC-LOG-AUTOANALYZE-MIN-DURATION", "path": "runtime-config-logging.html", "label": "Related global parameter: log_autoanalyze_min_duration", "sha256": "e50a8a5efff74a4907d31c32dc399e8e9974a0df3a1eb2e021afd34f56ed0918"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: log_autoanalyze_min_duration", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Causes analyze action executed by autovacuum to be logged if it ran for at least the specified amount of time. Setting this to zero logs all analyze actions by autovacuum. -1 disables logging analyze actions by autovacuum. If this value is specified without units, it is taken as milliseconds. For example, if you set this to 250ms then all automatic analyzes that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1 , a message will be logged if an analyze action by autovacuum is skipped due to a conflicting lock or a concurrently dropped relation. The default is 10min . Enabling this parameter can be helpful in tracking analyze activity by autovacuum. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (log_autoanalyze_min_duration = value)", "description": ["Per-table value for log_autoanalyze_min_duration parameter."]}}, "content_hash": "2f8a0752bcfa74d92dbded750f06be97705744e5b56ffe3b76b7d054350a2873", "imported_at": "2026-09-27T09:57:58.960", "url": "/wiki/relopts/table-log-autoanalyze-min-duration/?v=18", "cells": [{"major": "10", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 10.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-log-autoanalyze-min-duration/?v=10"}, {"major": "11", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 11.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-log-autoanalyze-min-duration/?v=11"}, {"major": "12", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 12.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-log-autoanalyze-min-duration/?v=12"}, {"major": "13", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 13.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-log-autoanalyze-min-duration/?v=13"}, {"major": "14", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 14.24 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-log-autoanalyze-min-duration/?v=14"}, {"major": "15", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 15.19 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-log-autoanalyze-min-duration/?v=15"}, {"major": "16", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 16.15 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-log-autoanalyze-min-duration/?v=16"}, {"major": "17", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 17.11 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-log-autoanalyze-min-duration/?v=17"}, {"major": "18", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 18.6 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-log-autoanalyze-min-duration/?v=18"}, {"major": "19", "state": "added", "label": "First recorded in this sample", "title": "PostgreSQL 19 beta 4 \u00b7 First recorded in this sample", "url": "/wiki/relopts/table-log-autoanalyze-min-duration/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-log-autoanalyze-min-duration/?v=20"}], "present": false}, {"slug": "table-log-autovacuum-min-duration", "name": "log_autovacuum_min_duration", "name_zh": "log_autovacuum_min_duration", "category": "Tables and materialized views", "summary": "Per-table value for log_autovacuum_min_duration parameter.", "aliases": ["table.log_autovacuum_min_duration"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/log_autovacuum_min_duration/?v=10", "label": "Global parameter log_autovacuum_min_duration"}, {"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/runtime-config-autovacuum.html#GUC-LOG-AUTOVACUUM-MIN-DURATION", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: log_autovacuum_min_duration", "sha256": "a8c8d51fd43c0e169a2ce6bcb094c1dbd5f0f6cd6e90cabc86f6542039600355"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: log_autovacuum_min_duration", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Causes each action executed by autovacuum to be logged if it ran for at least the specified number of milliseconds. Setting this to zero logs all autovacuum actions. Minus-one (the default) disables logging autovacuum actions. For example, if you set this to 250ms then all automatic vacuums and analyzes that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1 , a message will be logged if an autovacuum action is skipped due to the existence of a conflicting lock. Enabling this parameter can be helpful in tracking autovacuum activity. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (log_autovacuum_min_duration = value)", "description": ["Per-table value for log_autovacuum_min_duration parameter."]}, "11": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/log_autovacuum_min_duration/?v=11", "label": "Global parameter log_autovacuum_min_duration"}, {"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/runtime-config-autovacuum.html#GUC-LOG-AUTOVACUUM-MIN-DURATION", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: log_autovacuum_min_duration", "sha256": "a553adbaa0edb4dbdf216a59031edf5974a2791c02e12f3a6f23a0df0cdc59d1"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}, {"title": "Related global parameter: log_autovacuum_min_duration", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Causes each action executed by autovacuum to be logged if it ran for at least the specified number of milliseconds. Setting this to zero logs all autovacuum actions. Minus-one (the default) disables logging autovacuum actions. For example, if you set this to 250ms then all automatic vacuums and analyzes that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1 , a message will be logged if an autovacuum action is skipped due to a conflicting lock or a concurrently dropped relation. Enabling this parameter can be helpful in tracking autovacuum activity. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (log_autovacuum_min_duration = value)", "description": ["Per-table value for log_autovacuum_min_duration parameter."]}, "12": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/log_autovacuum_min_duration/?v=12", "label": "Global parameter log_autovacuum_min_duration"}, {"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-LOG-AUTOVACUUM-MIN-DURATION", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/runtime-config-autovacuum.html#GUC-LOG-AUTOVACUUM-MIN-DURATION", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: log_autovacuum_min_duration", "sha256": "bb486d78e8d17e633e046674781b62e0cf0f77efbb48cd6fffa5fd6b34ac98e6"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: log_autovacuum_min_duration", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Causes each action executed by autovacuum to be logged if it ran for at least the specified amount of time. Setting this to zero logs all autovacuum actions. -1 (the default) disables logging autovacuum actions. If this value is specified without units, it is taken as milliseconds. For example, if you set this to 250ms then all automatic vacuums and analyzes that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1 , a message will be logged if an autovacuum action is skipped due to a conflicting lock or a concurrently dropped relation. Enabling this parameter can be helpful in tracking autovacuum activity. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (log_autovacuum_min_duration = value)", "description": ["Per-table value for log_autovacuum_min_duration parameter."]}, "13": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/log_autovacuum_min_duration/?v=13", "label": "Global parameter log_autovacuum_min_duration"}, {"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-LOG-AUTOVACUUM-MIN-DURATION", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/runtime-config-autovacuum.html#GUC-LOG-AUTOVACUUM-MIN-DURATION", "path": "runtime-config-autovacuum.html", "label": "Related global parameter: log_autovacuum_min_duration", "sha256": "d26d014ad3850d3dbbbc1bce41bc267205baa1523b73e48fdd9e7165b6f6785e"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: log_autovacuum_min_duration", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Causes each action executed by autovacuum to be logged if it ran for at least the specified amount of time. Setting this to zero logs all autovacuum actions. -1 (the default) disables logging autovacuum actions. If this value is specified without units, it is taken as milliseconds. For example, if you set this to 250ms then all automatic vacuums and analyzes that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1 , a message will be logged if an autovacuum action is skipped due to a conflicting lock or a concurrently dropped relation. Enabling this parameter can be helpful in tracking autovacuum activity. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (log_autovacuum_min_duration = value)", "description": ["Per-table value for log_autovacuum_min_duration parameter."]}, "14": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/log_autovacuum_min_duration/?v=14", "label": "Global parameter log_autovacuum_min_duration"}, {"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-LOG-AUTOVACUUM-MIN-DURATION", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/runtime-config-logging.html#GUC-LOG-AUTOVACUUM-MIN-DURATION", "path": "runtime-config-logging.html", "label": "Related global parameter: log_autovacuum_min_duration", "sha256": "d34de91c4a58cce28aa78480bd98391b5ccad1a35490835101d8d786cd119c29"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: log_autovacuum_min_duration", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Causes each action executed by autovacuum to be logged if it ran for at least the specified amount of time. Setting this to zero logs all autovacuum actions. -1 (the default) disables logging autovacuum actions. If this value is specified without units, it is taken as milliseconds. For example, if you set this to 250ms then all automatic vacuums and analyzes that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1 , a message will be logged if an autovacuum action is skipped due to a conflicting lock or a concurrently dropped relation. Enabling this parameter can be helpful in tracking autovacuum activity. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (log_autovacuum_min_duration = value)", "description": ["Per-table value for log_autovacuum_min_duration parameter."]}, "15": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/log_autovacuum_min_duration/?v=15", "label": "Global parameter log_autovacuum_min_duration"}, {"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-LOG-AUTOVACUUM-MIN-DURATION", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/runtime-config-logging.html#GUC-LOG-AUTOVACUUM-MIN-DURATION", "path": "runtime-config-logging.html", "label": "Related global parameter: log_autovacuum_min_duration", "sha256": "7ba3faabd0ae6bd7f5709873c4a59ff9573e69b3373f0dfe1758409cd64580f0"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: log_autovacuum_min_duration", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Causes each action executed by autovacuum to be logged if it ran for at least the specified amount of time. Setting this to zero logs all autovacuum actions. -1 disables logging autovacuum actions. If this value is specified without units, it is taken as milliseconds. For example, if you set this to 250ms then all automatic vacuums and analyzes that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1 , a message will be logged if an autovacuum action is skipped due to a conflicting lock or a concurrently dropped relation. The default is 10min . Enabling this parameter can be helpful in tracking autovacuum activity. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (log_autovacuum_min_duration = value)", "description": ["Per-table value for log_autovacuum_min_duration parameter."]}, "16": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/log_autovacuum_min_duration/?v=16", "label": "Global parameter log_autovacuum_min_duration"}, {"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-LOG-AUTOVACUUM-MIN-DURATION", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/runtime-config-logging.html#GUC-LOG-AUTOVACUUM-MIN-DURATION", "path": "runtime-config-logging.html", "label": "Related global parameter: log_autovacuum_min_duration", "sha256": "c8d8d9cc2d0adb4e157c6e9e073812844670d9c114ee25527f8266e010f691ec"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: log_autovacuum_min_duration", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Causes each action executed by autovacuum to be logged if it ran for at least the specified amount of time. Setting this to zero logs all autovacuum actions. -1 disables logging autovacuum actions. If this value is specified without units, it is taken as milliseconds. For example, if you set this to 250ms then all automatic vacuums and analyzes that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1 , a message will be logged if an autovacuum action is skipped due to a conflicting lock or a concurrently dropped relation. The default is 10min . Enabling this parameter can be helpful in tracking autovacuum activity. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (log_autovacuum_min_duration = value)", "description": ["Per-table value for log_autovacuum_min_duration parameter."]}, "17": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/log_autovacuum_min_duration/?v=17", "label": "Global parameter log_autovacuum_min_duration"}, {"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-LOG-AUTOVACUUM-MIN-DURATION", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/runtime-config-logging.html#GUC-LOG-AUTOVACUUM-MIN-DURATION", "path": "runtime-config-logging.html", "label": "Related global parameter: log_autovacuum_min_duration", "sha256": "a1791a4a78e8d1860821e85ed3b02fc93d9499434b36a19c03e50edca89759fe"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: log_autovacuum_min_duration", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Causes each action executed by autovacuum to be logged if it ran for at least the specified amount of time. Setting this to zero logs all autovacuum actions. -1 disables logging autovacuum actions. If this value is specified without units, it is taken as milliseconds. For example, if you set this to 250ms then all automatic vacuums and analyzes that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1 , a message will be logged if an autovacuum action is skipped due to a conflicting lock or a concurrently dropped relation. The default is 10min . Enabling this parameter can be helpful in tracking autovacuum activity. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (log_autovacuum_min_duration = value)", "description": ["Per-table value for log_autovacuum_min_duration parameter."]}, "18": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/log_autovacuum_min_duration/?v=18", "label": "Global parameter log_autovacuum_min_duration"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-LOG-AUTOVACUUM-MIN-DURATION", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-logging.html#GUC-LOG-AUTOVACUUM-MIN-DURATION", "path": "runtime-config-logging.html", "label": "Related global parameter: log_autovacuum_min_duration", "sha256": "93c48c522a72fca19705c4c91a71e951eae653662008eee2e4a9a74a11127fde"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: log_autovacuum_min_duration", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Causes each action executed by autovacuum to be logged if it ran for at least the specified amount of time. Setting this to zero logs all autovacuum actions. -1 disables logging autovacuum actions. If this value is specified without units, it is taken as milliseconds. For example, if you set this to 250ms then all automatic vacuums and analyzes that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1 , a message will be logged if an autovacuum action is skipped due to a conflicting lock or a concurrently dropped relation. The default is 10min . Enabling this parameter can be helpful in tracking autovacuum activity. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (log_autovacuum_min_duration = value)", "description": ["Per-table value for log_autovacuum_min_duration parameter."]}, "19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/log_autovacuum_min_duration/?v=19", "label": "Global parameter log_autovacuum_min_duration"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-LOG-AUTOVACUUM-MIN-DURATION", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-logging.html#GUC-LOG-AUTOVACUUM-MIN-DURATION", "path": "runtime-config-logging.html", "label": "Related global parameter: log_autovacuum_min_duration", "sha256": "6bc8c26ccff0749f936162b21d68912f6be287148245e296d602589f7782a116"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: log_autovacuum_min_duration", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Causes vacuum action executed by autovacuum to be logged if it ran for at least the specified amount of time. Setting this to zero logs all vacuum actions by autovacuum. -1 disables logging vacuum actions by autovacuum. If this value is specified without units, it is taken as milliseconds. For example, if you set this to 250ms then all automatic vacuums that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1 , a message will be logged if a vacuum action by autovacuum is skipped due to a conflicting lock or a concurrently dropped relation. The default is 10min . Enabling this parameter can be helpful in tracking vacuum activity by autovacuum. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (log_autovacuum_min_duration = value)", "description": ["Per-table value for log_autovacuum_min_duration parameter."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/guc/log_autovacuum_min_duration/?v=20", "label": "Global parameter log_autovacuum_min_duration"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-LOG-AUTOVACUUM-MIN-DURATION", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-logging.html#GUC-LOG-AUTOVACUUM-MIN-DURATION", "path": "runtime-config-logging.html", "label": "Related global parameter: log_autovacuum_min_duration", "sha256": "e50a8a5efff74a4907d31c32dc399e8e9974a0df3a1eb2e021afd34f56ed0918"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: log_autovacuum_min_duration", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Causes vacuum action executed by autovacuum to be logged if it ran for at least the specified amount of time. Setting this to zero logs all vacuum actions by autovacuum. -1 disables logging vacuum actions by autovacuum. If this value is specified without units, it is taken as milliseconds. For example, if you set this to 250ms then all automatic vacuums that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1 , a message will be logged if a vacuum action by autovacuum is skipped due to a conflicting lock or a concurrently dropped relation. The default is 10min . Enabling this parameter can be helpful in tracking vacuum activity by autovacuum. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (log_autovacuum_min_duration = value)", "description": ["Per-table value for log_autovacuum_min_duration parameter."]}}, "content_hash": "d33bbd1b84b8a4fd7625d756fae0fad541a04b4600586cd98096bb7d6d96b7cd", "imported_at": "2026-09-27T09:57:58.962", "url": "/wiki/relopts/table-log-autovacuum-min-duration/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/table-log-autovacuum-min-duration/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/table-log-autovacuum-min-duration/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/table-log-autovacuum-min-duration/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/table-log-autovacuum-min-duration/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/table-log-autovacuum-min-duration/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/table-log-autovacuum-min-duration/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/table-log-autovacuum-min-duration/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/table-log-autovacuum-min-duration/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/table-log-autovacuum-min-duration/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-log-autovacuum-min-duration/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-log-autovacuum-min-duration/?v=20"}], "present": true}, {"slug": "table-parallel-workers", "name": "parallel_workers", "name_zh": "parallel_workers", "category": "Tables and materialized views", "summary": "This sets the number of workers that should be used to assist a parallel scan of this table. If not set, the system will determine a value based on the relation size. The actual number of workers chosen by the planner or by utility statements that use parallel scans may be less, for example due to the setting of max_worker_processes .", "aliases": ["table.parallel_workers"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}], "signature": "WITH (parallel_workers = value)", "description": ["This sets the number of workers that should be used to assist a parallel scan of this table. If not set, the system will determine a value based on the relation size. The actual number of workers chosen by the planner may be less, for example due to the setting of max_worker_processes ."]}, "11": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}], "signature": "WITH (parallel_workers = value)", "description": ["This sets the number of workers that should be used to assist a parallel scan of this table. If not set, the system will determine a value based on the relation size. The actual number of workers chosen by the planner or by utility statements that use parallel scans may be less, for example due to the setting of max_worker_processes ."]}, "12": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-PARALLEL-WORKERS", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (parallel_workers = value)", "description": ["This sets the number of workers that should be used to assist a parallel scan of this table. If not set, the system will determine a value based on the relation size. The actual number of workers chosen by the planner or by utility statements that use parallel scans may be less, for example due to the setting of max_worker_processes ."]}, "13": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-PARALLEL-WORKERS", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (parallel_workers = value)", "description": ["This sets the number of workers that should be used to assist a parallel scan of this table. If not set, the system will determine a value based on the relation size. The actual number of workers chosen by the planner or by utility statements that use parallel scans may be less, for example due to the setting of max_worker_processes ."]}, "14": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-PARALLEL-WORKERS", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (parallel_workers = value)", "description": ["This sets the number of workers that should be used to assist a parallel scan of this table. If not set, the system will determine a value based on the relation size. The actual number of workers chosen by the planner or by utility statements that use parallel scans may be less, for example due to the setting of max_worker_processes ."]}, "15": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-PARALLEL-WORKERS", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (parallel_workers = value)", "description": ["This sets the number of workers that should be used to assist a parallel scan of this table. If not set, the system will determine a value based on the relation size. The actual number of workers chosen by the planner or by utility statements that use parallel scans may be less, for example due to the setting of max_worker_processes ."]}, "16": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-PARALLEL-WORKERS", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (parallel_workers = value)", "description": ["This sets the number of workers that should be used to assist a parallel scan of this table. If not set, the system will determine a value based on the relation size. The actual number of workers chosen by the planner or by utility statements that use parallel scans may be less, for example due to the setting of max_worker_processes ."]}, "17": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-PARALLEL-WORKERS", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (parallel_workers = value)", "description": ["This sets the number of workers that should be used to assist a parallel scan of this table. If not set, the system will determine a value based on the relation size. The actual number of workers chosen by the planner or by utility statements that use parallel scans may be less, for example due to the setting of max_worker_processes ."]}, "18": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-PARALLEL-WORKERS", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (parallel_workers = value)", "description": ["This sets the number of workers that should be used to assist a parallel scan of this table. If not set, the system will determine a value based on the relation size. The actual number of workers chosen by the planner or by utility statements that use parallel scans may be less, for example due to the setting of max_worker_processes ."]}, "19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-PARALLEL-WORKERS", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (parallel_workers = value)", "description": ["This sets the number of workers that should be used to assist a parallel scan of this table. If not set, the system will determine a value based on the relation size. The actual number of workers chosen by the planner or by utility statements that use parallel scans may be less, for example due to the setting of max_worker_processes ."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-PARALLEL-WORKERS", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (parallel_workers = value)", "description": ["This sets the number of workers that should be used to assist a parallel scan of this table. If not set, the system will determine a value based on the relation size. The actual number of workers chosen by the planner or by utility statements that use parallel scans may be less, for example due to the setting of max_worker_processes ."]}}, "content_hash": "e442884c533b53814ac089214b80abdae966447c410f206c9a3c182e79ddc6e2", "imported_at": "2026-09-27T09:57:58.966", "url": "/wiki/relopts/table-parallel-workers/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/table-parallel-workers/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/table-parallel-workers/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/table-parallel-workers/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/table-parallel-workers/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/table-parallel-workers/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/table-parallel-workers/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/table-parallel-workers/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/table-parallel-workers/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/table-parallel-workers/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-parallel-workers/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-parallel-workers/?v=20"}], "present": true}, {"slug": "table-toast-tuple-target", "name": "toast_tuple_target", "name_zh": "toast_tuple_target", "category": "Tables and materialized views", "summary": "The toast_tuple_target specifies the minimum tuple length required before we try to compress and/or move long column values into TOAST tables, and is also the target length we try to reduce the length below once toasting begins. This affects columns marked as External (for move), Main (for compression), or Extended (for both) and applies only to new tuples. There is no effect on existing rows. By default this parameter is set to allow at least 4 tuples per block, which with the default block size will be 2040 bytes. Valid values are between 128 bytes and the (block size - header), by default 8160 bytes. Changing this value may not be useful for very short or very long rows. Note that the default setting is often close to optimal, and it is possible that setting this parameter could have negative effects in some cases. This parameter cannot be set for TOAST tables.", "aliases": ["table.toast_tuple_target"], "versions": {"11": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}], "signature": "WITH (toast_tuple_target = value)", "description": ["The toast_tuple_target specifies the minimum tuple length required before we try to compress and/or move long column values into TOAST tables, and is also the target length we try to reduce the length below once toasting begins. This affects columns marked as External (for move), Main (for compression), or Extended (for both) and applies only to new tuples. There is no effect on existing rows. By default this parameter is set to allow at least 4 tuples per block, which with the default blocksize will be 2040 bytes. Valid values are between 128 bytes and the (blocksize - header), by default 8160 bytes. Changing this value may not be useful for very short or very long rows. Note that the default setting is often close to optimal, and it is possible that setting this parameter could have negative effects in some cases. This parameter cannot be set for TOAST tables."]}, "12": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-TOAST-TUPLE-TARGET", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast_tuple_target = value)", "description": ["The toast_tuple_target specifies the minimum tuple length required before we try to compress and/or move long column values into TOAST tables, and is also the target length we try to reduce the length below once toasting begins. This affects columns marked as External (for move), Main (for compression), or Extended (for both) and applies only to new tuples. There is no effect on existing rows. By default this parameter is set to allow at least 4 tuples per block, which with the default blocksize will be 2040 bytes. Valid values are between 128 bytes and the (blocksize - header), by default 8160 bytes. Changing this value may not be useful for very short or very long rows. Note that the default setting is often close to optimal, and it is possible that setting this parameter could have negative effects in some cases. This parameter cannot be set for TOAST tables."]}, "13": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-TOAST-TUPLE-TARGET", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast_tuple_target = value)", "description": ["The toast_tuple_target specifies the minimum tuple length required before we try to compress and/or move long column values into TOAST tables, and is also the target length we try to reduce the length below once toasting begins. This affects columns marked as External (for move), Main (for compression), or Extended (for both) and applies only to new tuples. There is no effect on existing rows. By default this parameter is set to allow at least 4 tuples per block, which with the default block size will be 2040 bytes. Valid values are between 128 bytes and the (block size - header), by default 8160 bytes. Changing this value may not be useful for very short or very long rows. Note that the default setting is often close to optimal, and it is possible that setting this parameter could have negative effects in some cases. This parameter cannot be set for TOAST tables."]}, "14": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-TOAST-TUPLE-TARGET", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast_tuple_target = value)", "description": ["The toast_tuple_target specifies the minimum tuple length required before we try to compress and/or move long column values into TOAST tables, and is also the target length we try to reduce the length below once toasting begins. This affects columns marked as External (for move), Main (for compression), or Extended (for both) and applies only to new tuples. There is no effect on existing rows. By default this parameter is set to allow at least 4 tuples per block, which with the default block size will be 2040 bytes. Valid values are between 128 bytes and the (block size - header), by default 8160 bytes. Changing this value may not be useful for very short or very long rows. Note that the default setting is often close to optimal, and it is possible that setting this parameter could have negative effects in some cases. This parameter cannot be set for TOAST tables."]}, "15": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-TOAST-TUPLE-TARGET", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast_tuple_target = value)", "description": ["The toast_tuple_target specifies the minimum tuple length required before we try to compress and/or move long column values into TOAST tables, and is also the target length we try to reduce the length below once toasting begins. This affects columns marked as External (for move), Main (for compression), or Extended (for both) and applies only to new tuples. There is no effect on existing rows. By default this parameter is set to allow at least 4 tuples per block, which with the default block size will be 2040 bytes. Valid values are between 128 bytes and the (block size - header), by default 8160 bytes. Changing this value may not be useful for very short or very long rows. Note that the default setting is often close to optimal, and it is possible that setting this parameter could have negative effects in some cases. This parameter cannot be set for TOAST tables."]}, "16": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-TOAST-TUPLE-TARGET", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast_tuple_target = value)", "description": ["The toast_tuple_target specifies the minimum tuple length required before we try to compress and/or move long column values into TOAST tables, and is also the target length we try to reduce the length below once toasting begins. This affects columns marked as External (for move), Main (for compression), or Extended (for both) and applies only to new tuples. There is no effect on existing rows. By default this parameter is set to allow at least 4 tuples per block, which with the default block size will be 2040 bytes. Valid values are between 128 bytes and the (block size - header), by default 8160 bytes. Changing this value may not be useful for very short or very long rows. Note that the default setting is often close to optimal, and it is possible that setting this parameter could have negative effects in some cases. This parameter cannot be set for TOAST tables."]}, "17": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-TOAST-TUPLE-TARGET", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast_tuple_target = value)", "description": ["The toast_tuple_target specifies the minimum tuple length required before we try to compress and/or move long column values into TOAST tables, and is also the target length we try to reduce the length below once toasting begins. This affects columns marked as External (for move), Main (for compression), or Extended (for both) and applies only to new tuples. There is no effect on existing rows. By default this parameter is set to allow at least 4 tuples per block, which with the default block size will be 2040 bytes. Valid values are between 128 bytes and the (block size - header), by default 8160 bytes. Changing this value may not be useful for very short or very long rows. Note that the default setting is often close to optimal, and it is possible that setting this parameter could have negative effects in some cases. This parameter cannot be set for TOAST tables."]}, "18": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-TOAST-TUPLE-TARGET", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast_tuple_target = value)", "description": ["The toast_tuple_target specifies the minimum tuple length required before we try to compress and/or move long column values into TOAST tables, and is also the target length we try to reduce the length below once toasting begins. This affects columns marked as External (for move), Main (for compression), or Extended (for both) and applies only to new tuples. There is no effect on existing rows. By default this parameter is set to allow at least 4 tuples per block, which with the default block size will be 2040 bytes. Valid values are between 128 bytes and the (block size - header), by default 8160 bytes. Changing this value may not be useful for very short or very long rows. Note that the default setting is often close to optimal, and it is possible that setting this parameter could have negative effects in some cases. This parameter cannot be set for TOAST tables."]}, "19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-TOAST-TUPLE-TARGET", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast_tuple_target = value)", "description": ["The toast_tuple_target specifies the minimum tuple length required before we try to compress and/or move long column values into TOAST tables, and is also the target length we try to reduce the length below once toasting begins. This affects columns marked as External (for move), Main (for compression), or Extended (for both) and applies only to new tuples. There is no effect on existing rows. By default this parameter is set to allow at least 4 tuples per block, which with the default block size will be 2040 bytes. Valid values are between 128 bytes and the (block size - header), by default 8160 bytes. Changing this value may not be useful for very short or very long rows. Note that the default setting is often close to optimal, and it is possible that setting this parameter could have negative effects in some cases. This parameter cannot be set for TOAST tables."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "integer"}], "related": [{"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-TOAST-TUPLE-TARGET", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast_tuple_target = value)", "description": ["The toast_tuple_target specifies the minimum tuple length required before we try to compress and/or move long column values into TOAST tables, and is also the target length we try to reduce the length below once toasting begins. This affects columns marked as External (for move), Main (for compression), or Extended (for both) and applies only to new tuples. There is no effect on existing rows. By default this parameter is set to allow at least 4 tuples per block, which with the default block size will be 2040 bytes. Valid values are between 128 bytes and the (block size - header), by default 8160 bytes. Changing this value may not be useful for very short or very long rows. Note that the default setting is often close to optimal, and it is possible that setting this parameter could have negative effects in some cases. This parameter cannot be set for TOAST tables."]}}, "content_hash": "14652cb4b112e1bf62ff048bc36d2ab84b9273d3b8fed21575c2cfd6044e4d5a", "imported_at": "2026-09-27T09:57:58.968", "url": "/wiki/relopts/table-toast-tuple-target/?v=18", "cells": [{"major": "10", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 10.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-toast-tuple-target/?v=10"}, {"major": "11", "state": "added", "label": "First recorded in this sample", "title": "PostgreSQL 11.22 \u00b7 First recorded in this sample", "url": "/wiki/relopts/table-toast-tuple-target/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/table-toast-tuple-target/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/table-toast-tuple-target/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/table-toast-tuple-target/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/table-toast-tuple-target/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/table-toast-tuple-target/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/table-toast-tuple-target/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/table-toast-tuple-target/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-toast-tuple-target/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-toast-tuple-target/?v=20"}], "present": true}, {"slug": "table-toast-value-type", "name": "toast_value_type", "name_zh": "toast_value_type", "category": "Tables and materialized views", "summary": "Not recorded in the selected version.", "aliases": ["table.toast_value_type"], "versions": {"20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "enum"}], "related": [{"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-TOAST-VALUE-TYPE", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (toast_value_type = value)", "description": ["Specifies the attribute type of chunk_id to use when creating a TOAST relation for this table. The default is oid ; oid8 assigns oid8 instead, which allows a larger number of distinct TOAST ed values at the price of four extra bytes per out-of-line pointer. This parameter cannot be set for TOAST tables.", "The value is only consulted when the TOAST relation is created. Changing it afterwards has no effect on an existing TOAST relation, and a table rewrite such as CLUSTER , REPACK or VACUUM FULL preserves the type already in use. A dump and restore, on the other hand, recreates the TOAST relation and therefore applies the current value of this parameter."]}}, "content_hash": "3a73612a43c15b98d975a8b6e4edc7d09ef35f71c87d163fa20a4467b7861529", "imported_at": "2026-09-27T09:57:58.970", "url": "/wiki/relopts/table-toast-value-type/?v=18", "cells": [{"major": "10", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 10.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-toast-value-type/?v=10"}, {"major": "11", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 11.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-toast-value-type/?v=11"}, {"major": "12", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 12.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-toast-value-type/?v=12"}, {"major": "13", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 13.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-toast-value-type/?v=13"}, {"major": "14", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 14.24 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-toast-value-type/?v=14"}, {"major": "15", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 15.19 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-toast-value-type/?v=15"}, {"major": "16", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 16.15 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-toast-value-type/?v=16"}, {"major": "17", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 17.11 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-toast-value-type/?v=17"}, {"major": "18", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 18.6 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-toast-value-type/?v=18"}, {"major": "19", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 19 beta 4 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-toast-value-type/?v=19"}, {"major": "20", "state": "added", "label": "First recorded in this sample", "title": "PostgreSQL 20 devel \u00b7 First recorded in this sample", "url": "/wiki/relopts/table-toast-value-type/?v=20"}], "present": false}, {"slug": "table-user-catalog-table", "name": "user_catalog_table", "name_zh": "user_catalog_table", "category": "Tables and materialized views", "summary": "Declare the table as an additional catalog table for purposes of logical replication. See Section 47.6.2 for details. This parameter cannot be set for TOAST tables.", "aliases": ["table.user_catalog_table"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=10", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 10 English manual", "sha256": "6a9df6e68f8acd82ca864475616f6c1cf483c97f96abfc2c2abd565aeb4129a5"}, {"url": "/docs/10/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 10 English manual", "sha256": "46695b2591db26e272812f8d72ebfb2f37bbbf419123ff71792fe0af027ce785"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 67.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}], "signature": "WITH (user_catalog_table = value)", "description": ["Declare the table as an additional catalog table for purposes of logical replication. See Section 48.6.2 for details. This parameter cannot be set for TOAST tables."]}, "11": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=11", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS", "path": "sql-createtable.html", "label": "PostgreSQL 11 English manual", "sha256": "46282e6bc95b6c42283c9fe7b79c31be21cafaa5a18dda82b7793cd21f400075"}, {"url": "/docs/11/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 11 English manual", "sha256": "c9718b3ccdec9aea0bff15bbe8c31ceaff935ebb0c2d372ce37101924aafe5d3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW with the exception of OIDS . See CREATE TABLE for more information."]}], "signature": "WITH (user_catalog_table = value)", "description": ["Declare the table as an additional catalog table for purposes of logical replication. See Section 49.6.2 for details. This parameter cannot be set for TOAST tables."]}, "12": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-USER-CATALOG-TABLE", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (user_catalog_table = value)", "description": ["Declare the table as an additional catalog table for purposes of logical replication. See Section 48.6.2 for details. This parameter cannot be set for TOAST tables."]}, "13": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-USER-CATALOG-TABLE", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (user_catalog_table = value)", "description": ["Declare the table as an additional catalog table for purposes of logical replication. See Section 48.6.2 for details. This parameter cannot be set for TOAST tables."]}, "14": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-USER-CATALOG-TABLE", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (user_catalog_table = value)", "description": ["Declare the table as an additional catalog table for purposes of logical replication. See Section 49.6.2 for details. This parameter cannot be set for TOAST tables."]}, "15": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-USER-CATALOG-TABLE", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (user_catalog_table = value)", "description": ["Declare the table as an additional catalog table for purposes of logical replication. See Section 49.6.2 for details. This parameter cannot be set for TOAST tables."]}, "16": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-USER-CATALOG-TABLE", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (user_catalog_table = value)", "description": ["Declare the table as an additional catalog table for purposes of logical replication. See Section 49.6.2 for details. This parameter cannot be set for TOAST tables."]}, "17": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-USER-CATALOG-TABLE", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (user_catalog_table = value)", "description": ["Declare the table as an additional catalog table for purposes of logical replication. See Section 47.6.2 for details. This parameter cannot be set for TOAST tables."]}, "18": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-USER-CATALOG-TABLE", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (user_catalog_table = value)", "description": ["Declare the table as an additional catalog table for purposes of logical replication. See Section 47.6.2 for details. This parameter cannot be set for TOAST tables."]}, "19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-USER-CATALOG-TABLE", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (user_catalog_table = value)", "description": ["Declare the table as an additional catalog table for purposes of logical replication. See Section 47.7.2 for details. This parameter cannot be set for TOAST tables."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-USER-CATALOG-TABLE", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (user_catalog_table = value)", "description": ["Declare the table as an additional catalog table for purposes of logical replication. See Section 47.7.2 for details. This parameter cannot be set for TOAST tables."]}}, "content_hash": "2fded0f3454142ebe01e5212383d31ddf858a58b329833734dad7e584ee1b87e", "imported_at": "2026-09-27T09:57:58.972", "url": "/wiki/relopts/table-user-catalog-table/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/table-user-catalog-table/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/table-user-catalog-table/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/table-user-catalog-table/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/table-user-catalog-table/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/table-user-catalog-table/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/table-user-catalog-table/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/table-user-catalog-table/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/table-user-catalog-table/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/table-user-catalog-table/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-user-catalog-table/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-user-catalog-table/?v=20"}], "present": true}, {"slug": "table-vacuum-index-cleanup", "name": "vacuum_index_cleanup", "name_zh": "vacuum_index_cleanup", "category": "Tables and materialized views", "summary": "Forces or disables index cleanup when VACUUM is run on this table. The default value is AUTO . With OFF , index cleanup is disabled, with ON it is enabled, and with AUTO a decision is made dynamically, each time VACUUM runs. The dynamic behavior allows VACUUM to avoid needlessly scanning indexes to remove very few dead tuples. Forcibly disabling all index cleanup can speed up VACUUM very significantly, but may also lead to severely bloated indexes if table modifications are frequent. The INDEX_CLEANUP parameter of VACUUM , if specified, overrides the value of this option.", "aliases": ["table.vacuum_index_cleanup"], "versions": {"12": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-VACUUM-INDEX-CLEANUP", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (vacuum_index_cleanup = value)", "description": ["Enables or disables index cleanup when VACUUM is run on this table. The default value is true . Disabling index cleanup can speed up VACUUM very significantly, but may also lead to severely bloated indexes if table modifications are frequent. The INDEX_CLEANUP parameter of VACUUM , if specified, overrides the value of this option."]}, "13": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-VACUUM-INDEX-CLEANUP", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (vacuum_index_cleanup = value)", "description": ["Enables or disables index cleanup when VACUUM is run on this table. The default value is true . Disabling index cleanup can speed up VACUUM very significantly, but may also lead to severely bloated indexes if table modifications are frequent. The INDEX_CLEANUP parameter of VACUUM , if specified, overrides the value of this option."]}, "14": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "enum"}], "related": [{"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-VACUUM-INDEX-CLEANUP", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (vacuum_index_cleanup = value)", "description": ["Forces or disables index cleanup when VACUUM is run on this table. The default value is AUTO . With OFF , index cleanup is disabled, with ON it is enabled, and with AUTO a decision is made dynamically, each time VACUUM runs. The dynamic behavior allows VACUUM to avoid needlessly scanning indexes to remove very few dead tuples. Forcibly disabling all index cleanup can speed up VACUUM very significantly, but may also lead to severely bloated indexes if table modifications are frequent. The INDEX_CLEANUP parameter of VACUUM , if specified, overrides the value of this option."]}, "15": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "enum"}], "related": [{"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-VACUUM-INDEX-CLEANUP", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (vacuum_index_cleanup = value)", "description": ["Forces or disables index cleanup when VACUUM is run on this table. The default value is AUTO . With OFF , index cleanup is disabled, with ON it is enabled, and with AUTO a decision is made dynamically, each time VACUUM runs. The dynamic behavior allows VACUUM to avoid needlessly scanning indexes to remove very few dead tuples. Forcibly disabling all index cleanup can speed up VACUUM very significantly, but may also lead to severely bloated indexes if table modifications are frequent. The INDEX_CLEANUP parameter of VACUUM , if specified, overrides the value of this option."]}, "16": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "enum"}], "related": [{"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-VACUUM-INDEX-CLEANUP", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (vacuum_index_cleanup = value)", "description": ["Forces or disables index cleanup when VACUUM is run on this table. The default value is AUTO . With OFF , index cleanup is disabled, with ON it is enabled, and with AUTO a decision is made dynamically, each time VACUUM runs. The dynamic behavior allows VACUUM to avoid needlessly scanning indexes to remove very few dead tuples. Forcibly disabling all index cleanup can speed up VACUUM very significantly, but may also lead to severely bloated indexes if table modifications are frequent. The INDEX_CLEANUP parameter of VACUUM , if specified, overrides the value of this option."]}, "17": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "enum"}], "related": [{"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-VACUUM-INDEX-CLEANUP", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (vacuum_index_cleanup = value)", "description": ["Forces or disables index cleanup when VACUUM is run on this table. The default value is AUTO . With OFF , index cleanup is disabled, with ON it is enabled, and with AUTO a decision is made dynamically, each time VACUUM runs. The dynamic behavior allows VACUUM to avoid needlessly scanning indexes to remove very few dead tuples. Forcibly disabling all index cleanup can speed up VACUUM very significantly, but may also lead to severely bloated indexes if table modifications are frequent. The INDEX_CLEANUP parameter of VACUUM , if specified, overrides the value of this option."]}, "18": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "enum"}], "related": [{"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-VACUUM-INDEX-CLEANUP", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (vacuum_index_cleanup = value)", "description": ["Forces or disables index cleanup when VACUUM is run on this table. The default value is AUTO . With OFF , index cleanup is disabled, with ON it is enabled, and with AUTO a decision is made dynamically, each time VACUUM runs. The dynamic behavior allows VACUUM to avoid needlessly scanning indexes to remove very few dead tuples. Forcibly disabling all index cleanup can speed up VACUUM very significantly, but may also lead to severely bloated indexes if table modifications are frequent. The INDEX_CLEANUP parameter of VACUUM , if specified, overrides the value of this option."]}, "19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "enum"}], "related": [{"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-VACUUM-INDEX-CLEANUP", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (vacuum_index_cleanup = value)", "description": ["Forces or disables index cleanup when VACUUM is run on this table. The default value is AUTO . With OFF , index cleanup is disabled, with ON it is enabled, and with AUTO a decision is made dynamically, each time VACUUM runs. The dynamic behavior allows VACUUM to avoid needlessly scanning indexes to remove very few dead tuples. Forcibly disabling all index cleanup can speed up VACUUM very significantly, but may also lead to severely bloated indexes if table modifications are frequent. The INDEX_CLEANUP parameter of VACUUM , if specified, overrides the value of this option."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "enum"}], "related": [{"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-VACUUM-INDEX-CLEANUP", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (vacuum_index_cleanup = value)", "description": ["Forces or disables index cleanup when VACUUM is run on this table. The default value is AUTO . With OFF , index cleanup is disabled, with ON it is enabled, and with AUTO a decision is made dynamically, each time VACUUM runs. The dynamic behavior allows VACUUM to avoid needlessly scanning indexes to remove very few dead tuples. Forcibly disabling all index cleanup can speed up VACUUM very significantly, but may also lead to severely bloated indexes if table modifications are frequent. The INDEX_CLEANUP parameter of VACUUM , if specified, overrides the value of this option."]}}, "content_hash": "6b64e0ac50bf369dd535ba76b1e3185732280aaf3a6d059db593776725d6422d", "imported_at": "2026-09-27T09:57:58.974", "url": "/wiki/relopts/table-vacuum-index-cleanup/?v=18", "cells": [{"major": "10", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 10.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-vacuum-index-cleanup/?v=10"}, {"major": "11", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 11.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-vacuum-index-cleanup/?v=11"}, {"major": "12", "state": "added", "label": "First recorded in this sample", "title": "PostgreSQL 12.22 \u00b7 First recorded in this sample", "url": "/wiki/relopts/table-vacuum-index-cleanup/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/table-vacuum-index-cleanup/?v=13"}, {"major": "14", "state": "changed", "label": "Interface or attribute change", "title": "PostgreSQL 14.24 \u00b7 Interface or attribute change", "url": "/wiki/relopts/table-vacuum-index-cleanup/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/table-vacuum-index-cleanup/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/table-vacuum-index-cleanup/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/table-vacuum-index-cleanup/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/table-vacuum-index-cleanup/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-vacuum-index-cleanup/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-vacuum-index-cleanup/?v=20"}], "present": true}, {"slug": "table-vacuum-max-eager-freeze-failure-rate", "name": "vacuum_max_eager_freeze_failure_rate", "name_zh": "vacuum_max_eager_freeze_failure_rate", "category": "Tables and materialized views", "summary": "Per-table value for vacuum_max_eager_freeze_failure_rate parameter.", "aliases": ["table.vacuum_max_eager_freeze_failure_rate"], "versions": {"18": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/vacuum_max_eager_freeze_failure_rate/?v=18", "label": "Global parameter vacuum_max_eager_freeze_failure_rate"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-VACUUM-MAX-EAGER-FREEZE-FAILURE-RATE", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-VACUUM-MAX-EAGER-FREEZE-FAILURE-RATE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_max_eager_freeze_failure_rate", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_max_eager_freeze_failure_rate", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum number of pages (as a fraction of total pages in the relation) that VACUUM may scan and fail to set all-frozen in the visibility map before disabling eager scanning. A value of 0 disables eager scanning altogether. The default is 0.03 (3%).", "Note that when eager scanning is enabled, only freeze failures count against the cap, not successful freezing. Successful page freezes are capped internally at 20% of the all-visible but not all-frozen pages in the relation. Capping successful page freezes helps amortize the overhead across multiple normal vacuums and limits the potential downside of wasted eager freezes of pages that are modified again before the next aggressive vacuum.", "This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing the corresponding table storage parameter . For more information on tuning vacuum's freezing behavior, see Section 24.1.5 ."]}], "signature": "WITH (vacuum_max_eager_freeze_failure_rate = value)", "description": ["Per-table value for vacuum_max_eager_freeze_failure_rate parameter."]}, "19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/vacuum_max_eager_freeze_failure_rate/?v=19", "label": "Global parameter vacuum_max_eager_freeze_failure_rate"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-VACUUM-MAX-EAGER-FREEZE-FAILURE-RATE", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-VACUUM-MAX-EAGER-FREEZE-FAILURE-RATE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_max_eager_freeze_failure_rate", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_max_eager_freeze_failure_rate", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum number of pages (as a fraction of total pages in the relation) that VACUUM may scan and fail to set all-frozen in the visibility map before disabling eager scanning. A value of 0 disables eager scanning altogether. The default is 0.03 (3%).", "Note that when eager scanning is enabled, only freeze failures count against the cap, not successful freezing. Successful page freezes are capped internally at 20% of the all-visible but not all-frozen pages in the relation. Capping successful page freezes helps amortize the overhead across multiple normal vacuums and limits the potential downside of wasted eager freezes of pages that are modified again before the next aggressive vacuum.", "This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing the corresponding table storage parameter . For more information on tuning vacuum's freezing behavior, see Section 24.1.5 ."]}], "signature": "WITH (vacuum_max_eager_freeze_failure_rate = value)", "description": ["Per-table value for vacuum_max_eager_freeze_failure_rate parameter."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "floating point"}], "related": [{"url": "/docs/guc/vacuum_max_eager_freeze_failure_rate/?v=20", "label": "Global parameter vacuum_max_eager_freeze_failure_rate"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-VACUUM-MAX-EAGER-FREEZE-FAILURE-RATE", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-VACUUM-MAX-EAGER-FREEZE-FAILURE-RATE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_max_eager_freeze_failure_rate", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_max_eager_freeze_failure_rate", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Specifies the maximum number of pages (as a fraction of total pages in the relation) that VACUUM may scan and fail to set all-frozen in the visibility map before disabling eager scanning. A value of 0 disables eager scanning altogether. The default is 0.03 (3%).", "Note that when eager scanning is enabled, only freeze failures count against the cap, not successful freezing. Successful page freezes are capped internally at 20% of the all-visible but not all-frozen pages in the relation. Capping successful page freezes helps amortize the overhead across multiple normal vacuums and limits the potential downside of wasted eager freezes of pages that are modified again before the next aggressive vacuum.", "This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing the corresponding table storage parameter . For more information on tuning vacuum's freezing behavior, see Section 24.1.5 ."]}], "signature": "WITH (vacuum_max_eager_freeze_failure_rate = value)", "description": ["Per-table value for vacuum_max_eager_freeze_failure_rate parameter."]}}, "content_hash": "50ec8eaf273c0dd24ae487d249e9a5987cb7890f30ea821a060dcfd8db48c948", "imported_at": "2026-09-27T09:57:58.977", "url": "/wiki/relopts/table-vacuum-max-eager-freeze-failure-rate/?v=18", "cells": [{"major": "10", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 10.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-vacuum-max-eager-freeze-failure-rate/?v=10"}, {"major": "11", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 11.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-vacuum-max-eager-freeze-failure-rate/?v=11"}, {"major": "12", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 12.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-vacuum-max-eager-freeze-failure-rate/?v=12"}, {"major": "13", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 13.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-vacuum-max-eager-freeze-failure-rate/?v=13"}, {"major": "14", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 14.24 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-vacuum-max-eager-freeze-failure-rate/?v=14"}, {"major": "15", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 15.19 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-vacuum-max-eager-freeze-failure-rate/?v=15"}, {"major": "16", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 16.15 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-vacuum-max-eager-freeze-failure-rate/?v=16"}, {"major": "17", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 17.11 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-vacuum-max-eager-freeze-failure-rate/?v=17"}, {"major": "18", "state": "added", "label": "First recorded in this sample", "title": "PostgreSQL 18.6 \u00b7 First recorded in this sample", "url": "/wiki/relopts/table-vacuum-max-eager-freeze-failure-rate/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-vacuum-max-eager-freeze-failure-rate/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-vacuum-max-eager-freeze-failure-rate/?v=20"}], "present": true}, {"slug": "table-vacuum-truncate", "name": "vacuum_truncate", "name_zh": "vacuum_truncate", "category": "Tables and materialized views", "summary": "Per-table value for vacuum_truncate parameter. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this option.", "aliases": ["table.vacuum_truncate"], "versions": {"12": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=12", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createtable.html#RELOPTION-VACUUM-TRUNCATE", "path": "sql-createtable.html", "label": "PostgreSQL 12 English manual", "sha256": "7210cf3ff82ffa37ef81ebbbc252e4807649dcb86050eaa3ea5fcba40a768656"}, {"url": "/docs/12/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 12 English manual", "sha256": "2656497bc190ed29c24c29787f3ae68621830eee6345d291700c1ef8843f8dfe"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (vacuum_truncate = value)", "description": ["Enables or disables vacuum to try to truncate off any empty pages at the end of this table. The default value is true . If true , VACUUM and autovacuum do the truncation and the disk space for the truncated pages is returned to the operating system. Note that the truncation requires ACCESS EXCLUSIVE lock on the table. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this option."]}, "13": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=13", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createtable.html#RELOPTION-VACUUM-TRUNCATE", "path": "sql-createtable.html", "label": "PostgreSQL 13 English manual", "sha256": "912dd15faaa243438f33082160f2848636d1940afea42c36cf6d21a2a46c8cb8"}, {"url": "/docs/13/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 13 English manual", "sha256": "1d2de5d4ff709d2bab07b91c964d89ce8b9236d9aa99b83b79392d24d7b74fd3"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 69.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (vacuum_truncate = value)", "description": ["Enables or disables vacuum to try to truncate off any empty pages at the end of this table. The default value is true . If true , VACUUM and autovacuum do the truncation and the disk space for the truncated pages is returned to the operating system. Note that the truncation requires ACCESS EXCLUSIVE lock on the table. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this option."]}, "14": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=14", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createtable.html#RELOPTION-VACUUM-TRUNCATE", "path": "sql-createtable.html", "label": "PostgreSQL 14 English manual", "sha256": "2d92d1040e37f5d94ce279dc9f1555a720179397fcf3aa8412f5278ec1d943e8"}, {"url": "/docs/14/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 14 English manual", "sha256": "50aea483dd80c78b2bd3cac754341070bfc96e436139f0137d762b3f65834c3c"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 70.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (vacuum_truncate = value)", "description": ["Enables or disables vacuum to try to truncate off any empty pages at the end of this table. The default value is true . If true , VACUUM and autovacuum do the truncation and the disk space for the truncated pages is returned to the operating system. Note that the truncation requires ACCESS EXCLUSIVE lock on the table. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this option."]}, "15": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=15", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createtable.html#RELOPTION-VACUUM-TRUNCATE", "path": "sql-createtable.html", "label": "PostgreSQL 15 English manual", "sha256": "dcb246be9d6131c7227ccde6745458865a0c97ac4c8891c2cbea73a30769d6df"}, {"url": "/docs/15/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 15 English manual", "sha256": "9ce92d3a1afc7c70db12b6e3c2f163e2539cf86dbf0f1e9e6c44035b88bb10f7"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (vacuum_truncate = value)", "description": ["Enables or disables vacuum to try to truncate off any empty pages at the end of this table. The default value is true . If true , VACUUM and autovacuum do the truncation and the disk space for the truncated pages is returned to the operating system. Note that the truncation requires ACCESS EXCLUSIVE lock on the table. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this option."]}, "16": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=16", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createtable.html#RELOPTION-VACUUM-TRUNCATE", "path": "sql-createtable.html", "label": "PostgreSQL 16 English manual", "sha256": "dde6108abda6f7358eeccc6867eb68f5ca601329ea3f50bc3d5b728c944a65a8"}, {"url": "/docs/16/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 16 English manual", "sha256": "1a7ac648e9e3a49d0eab9de3b1214e1c64a16fc84fbee4c78c9f825b2c30af25"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 73.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (vacuum_truncate = value)", "description": ["Enables or disables vacuum to try to truncate off any empty pages at the end of this table. The default value is true . If true , VACUUM and autovacuum do the truncation and the disk space for the truncated pages is returned to the operating system. Note that the truncation requires ACCESS EXCLUSIVE lock on the table. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this option."]}, "17": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-table/?v=17", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createtable.html#RELOPTION-VACUUM-TRUNCATE", "path": "sql-createtable.html", "label": "PostgreSQL 17 English manual", "sha256": "97385c16a0ff155ad89fe616bb074bf0a8328bcb21f5e64a7a6a0a03ddb1f4ef"}, {"url": "/docs/17/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 17 English manual", "sha256": "88a9853b1cf1df2e9e468f5ef51e6f1932ffd000b37c298027a7cdef9bf0461f"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 65.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}], "signature": "WITH (vacuum_truncate = value)", "description": ["Enables or disables vacuum to try to truncate off any empty pages at the end of this table. The default value is true . If true , VACUUM and autovacuum do the truncation and the disk space for the truncated pages is returned to the operating system. Note that the truncation requires ACCESS EXCLUSIVE lock on the table. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this option."]}, "18": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/guc/vacuum_truncate/?v=18", "label": "Global parameter vacuum_truncate"}, {"url": "/docs/sql/create-table/?v=18", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createtable.html#RELOPTION-VACUUM-TRUNCATE", "path": "sql-createtable.html", "label": "PostgreSQL 18 English manual", "sha256": "b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b"}, {"url": "/docs/18/runtime-config-vacuum.html#GUC-VACUUM-TRUNCATE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_truncate", "sha256": "7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4"}, {"url": "/docs/18/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 18 English manual", "sha256": "bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_truncate", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Enables or disables vacuum to try to truncate off any empty pages at the end of the table. The default value is true . If true , VACUUM and autovacuum do the truncation and the disk space for the truncated pages is returned to the operating system. Note that the truncation requires an ACCESS EXCLUSIVE lock on the table. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this parameter. The setting can also be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (vacuum_truncate = value)", "description": ["Per-table value for vacuum_truncate parameter. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this option."]}, "19": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/guc/vacuum_truncate/?v=19", "label": "Global parameter vacuum_truncate"}, {"url": "/docs/sql/create-table/?v=19", "label": "CREATE TABLE"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createtable.html#RELOPTION-VACUUM-TRUNCATE", "path": "sql-createtable.html", "label": "PostgreSQL 19 English manual", "sha256": "75f290d105bd0e76c798f124b1eed4ad1e871c8a1d36c35f0db9d38fbb7209f8"}, {"url": "/docs/19/runtime-config-vacuum.html#GUC-VACUUM-TRUNCATE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_truncate", "sha256": "b4467324eaf7f51ab3a3086893b4db67d319aa05eb2cc51a6646a2085ff2b78e"}, {"url": "/docs/19/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 19 English manual", "sha256": "83626ff1539571da05619161c2d806590cac53ae060cea60018c6f63c6c02bf6"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_truncate", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Enables or disables vacuum to try to truncate off any empty pages at the end of the table. The default value is true . If true , VACUUM and autovacuum do the truncation and the disk space for the truncated pages is returned to the operating system. Note that the truncation requires an ACCESS EXCLUSIVE lock on the table. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this parameter. The setting can also be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (vacuum_truncate = value)", "description": ["Per-table value for vacuum_truncate parameter. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this option."]}, "20": {"facts": [{"label": "Applies to", "value": "Tables and materialized views"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/guc/vacuum_truncate/?v=20", "label": "Global parameter vacuum_truncate"}, {"url": "/docs/sql/create-table/?v=20", "label": "CREATE TABLE"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createtable.html#RELOPTION-VACUUM-TRUNCATE", "path": "sql-createtable.html", "label": "PostgreSQL 20 English manual", "sha256": "5241bd673de4e7a8fec7db6fa2a3a50d8368965206170725c4efd15d64c3fbf2"}, {"url": "/docs/devel/runtime-config-vacuum.html#GUC-VACUUM-TRUNCATE", "path": "runtime-config-vacuum.html", "label": "Related global parameter: vacuum_truncate", "sha256": "30e406323d744a69a54900ecb606fcabcf5c63c344644b82f72a45f8e0d9265d"}, {"url": "/docs/devel/sql-creatematerializedview.html", "path": "sql-creatematerializedview.html", "label": "PostgreSQL 20 English manual", "sha256": "2870e714f1d3ef3bb692310424bb0e8fc1905c7b4a46317c5be883c70daa90c2"}], "sections": [{"title": "Scope", "paragraphs": ["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."]}, {"title": "Common table storage rules", "paragraphs": ["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."]}, {"title": "Materialized views", "paragraphs": ["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."]}, {"title": "Related global parameter: vacuum_truncate", "paragraphs": ["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.", "Enables or disables vacuum to try to truncate off any empty pages at the end of the table. The default value is true . If true , VACUUM and autovacuum do the truncation and the disk space for the truncated pages is returned to the operating system. Note that the truncation requires an ACCESS EXCLUSIVE lock on the table. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this parameter. The setting can also be overridden for individual tables by changing table storage parameters."]}], "signature": "WITH (vacuum_truncate = value)", "description": ["Per-table value for vacuum_truncate parameter. The TRUNCATE parameter of VACUUM , if specified, overrides the value of this option."]}}, "content_hash": "7779e5be46130eef1d92186405c865b580046abd93b8f9cb57ef65ea7635a6c4", "imported_at": "2026-09-27T09:57:58.979", "url": "/wiki/relopts/table-vacuum-truncate/?v=18", "cells": [{"major": "10", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 10.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-vacuum-truncate/?v=10"}, {"major": "11", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 11.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/table-vacuum-truncate/?v=11"}, {"major": "12", "state": "added", "label": "First recorded in this sample", "title": "PostgreSQL 12.22 \u00b7 First recorded in this sample", "url": "/wiki/relopts/table-vacuum-truncate/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/table-vacuum-truncate/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/table-vacuum-truncate/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/table-vacuum-truncate/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/table-vacuum-truncate/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/table-vacuum-truncate/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/table-vacuum-truncate/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/table-vacuum-truncate/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/table-vacuum-truncate/?v=20"}], "present": true}, {"slug": "view-check-option", "name": "check_option", "name_zh": "check_option", "category": "View options", "summary": "This parameter may be either local or cascaded , and is equivalent to specifying WITH [ CASCADED | LOCAL ] CHECK OPTION (see below).", "aliases": ["view.check_option"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "string"}, {"label": "Values", "value": "local, cascaded"}], "related": [{"url": "/docs/sql/create-view/?v=10", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 10 English manual", "sha256": "f3beb72fc3c516331a0c0535d13aa59329eb7fdc265b20945dc7a37b97cfed4a"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Write checks", "paragraphs": ["This option controls the behavior of automatically updatable views. When this option is specified, INSERT and UPDATE commands on the view will be checked to ensure that new rows satisfy the view-defining condition (that is, the new rows are checked to ensure that they are visible through the view). If they are not, the update will be rejected. If the CHECK OPTION is not specified, INSERT and UPDATE commands on the view are allowed to create rows that are not visible through the view. The following check options are supported:", "LOCAL", "New rows are only checked against the conditions defined directly in the view itself. Any conditions defined on underlying base views are not checked (unless they also specify the CHECK OPTION ).", "CASCADED", "New rows are checked against the conditions of the view and all underlying base views. If the CHECK OPTION is specified, and neither LOCAL nor CASCADED is specified, then CASCADED is assumed.", "The CHECK OPTION may not be used with RECURSIVE views.", "Note that the CHECK OPTION is only supported on views that are automatically updatable, and do not have INSTEAD OF triggers or INSTEAD rules. If an automatically updatable view is defined on top of a base view that has INSTEAD OF triggers, then the LOCAL CHECK OPTION may be used to check the conditions on the automatically updatable view, but the conditions on the base view with INSTEAD OF triggers will not be checked (a cascaded check option will not cascade down to a trigger-updatable view, and any check options defined directly on a trigger-updatable view will be ignored). If the view or any of its base relations has an INSTEAD rule that causes the INSERT or UPDATE command to be rewritten, then all check options will be ignored in the rewritten query, including any checks from automatically updatable views defined on top of the relation with the INSTEAD rule."]}], "signature": "WITH (check_option = value)", "description": ["This parameter may be either local or cascaded , and is equivalent to specifying WITH [ CASCADED | LOCAL ] CHECK OPTION (see below). This option can be changed on existing views using ALTER VIEW ."]}, "11": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "string"}, {"label": "Values", "value": "local, cascaded"}], "related": [{"url": "/docs/sql/create-view/?v=11", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 11 English manual", "sha256": "cb691ccbc81965b50e4404c037e081b1038886bed54a2da7ed28d083ff11becd"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Write checks", "paragraphs": ["This option controls the behavior of automatically updatable views. When this option is specified, INSERT and UPDATE commands on the view will be checked to ensure that new rows satisfy the view-defining condition (that is, the new rows are checked to ensure that they are visible through the view). If they are not, the update will be rejected. If the CHECK OPTION is not specified, INSERT and UPDATE commands on the view are allowed to create rows that are not visible through the view. The following check options are supported:", "LOCAL", "New rows are only checked against the conditions defined directly in the view itself. Any conditions defined on underlying base views are not checked (unless they also specify the CHECK OPTION ).", "CASCADED", "New rows are checked against the conditions of the view and all underlying base views. If the CHECK OPTION is specified, and neither LOCAL nor CASCADED is specified, then CASCADED is assumed.", "The CHECK OPTION may not be used with RECURSIVE views.", "Note that the CHECK OPTION is only supported on views that are automatically updatable, and do not have INSTEAD OF triggers or INSTEAD rules. If an automatically updatable view is defined on top of a base view that has INSTEAD OF triggers, then the LOCAL CHECK OPTION may be used to check the conditions on the automatically updatable view, but the conditions on the base view with INSTEAD OF triggers will not be checked (a cascaded check option will not cascade down to a trigger-updatable view, and any check options defined directly on a trigger-updatable view will be ignored). If the view or any of its base relations has an INSTEAD rule that causes the INSERT or UPDATE command to be rewritten, then all check options will be ignored in the rewritten query, including any checks from automatically updatable views defined on top of the relation with the INSTEAD rule."]}], "signature": "WITH (check_option = value)", "description": ["This parameter may be either local or cascaded , and is equivalent to specifying WITH [ CASCADED | LOCAL ] CHECK OPTION (see below). This option can be changed on existing views using ALTER VIEW ."]}, "12": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "string"}, {"label": "Values", "value": "local, cascaded"}], "related": [{"url": "/docs/sql/create-view/?v=12", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 12 English manual", "sha256": "30c56ff14a8865b60f2954e70821eb7a6187fb35c2140b4c5697894b6f24bc9e"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Write checks", "paragraphs": ["This option controls the behavior of automatically updatable views. When this option is specified, INSERT and UPDATE commands on the view will be checked to ensure that new rows satisfy the view-defining condition (that is, the new rows are checked to ensure that they are visible through the view). If they are not, the update will be rejected. If the CHECK OPTION is not specified, INSERT and UPDATE commands on the view are allowed to create rows that are not visible through the view. The following check options are supported:", "LOCAL", "New rows are only checked against the conditions defined directly in the view itself. Any conditions defined on underlying base views are not checked (unless they also specify the CHECK OPTION ).", "CASCADED", "New rows are checked against the conditions of the view and all underlying base views. If the CHECK OPTION is specified, and neither LOCAL nor CASCADED is specified, then CASCADED is assumed.", "The CHECK OPTION may not be used with RECURSIVE views.", "Note that the CHECK OPTION is only supported on views that are automatically updatable, and do not have INSTEAD OF triggers or INSTEAD rules. If an automatically updatable view is defined on top of a base view that has INSTEAD OF triggers, then the LOCAL CHECK OPTION may be used to check the conditions on the automatically updatable view, but the conditions on the base view with INSTEAD OF triggers will not be checked (a cascaded check option will not cascade down to a trigger-updatable view, and any check options defined directly on a trigger-updatable view will be ignored). If the view or any of its base relations has an INSTEAD rule that causes the INSERT or UPDATE command to be rewritten, then all check options will be ignored in the rewritten query, including any checks from automatically updatable views defined on top of the relation with the INSTEAD rule."]}], "signature": "WITH (check_option = value)", "description": ["This parameter may be either local or cascaded , and is equivalent to specifying WITH [ CASCADED | LOCAL ] CHECK OPTION (see below). This option can be changed on existing views using ALTER VIEW ."]}, "13": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "enum"}, {"label": "Values", "value": "local, cascaded"}], "related": [{"url": "/docs/sql/create-view/?v=13", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 13 English manual", "sha256": "99ec0fd97653a0486c7d2575acc9713f73e2a9b12464e4dfa0b2046e772fd111"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Write checks", "paragraphs": ["This option controls the behavior of automatically updatable views. When this option is specified, INSERT and UPDATE commands on the view will be checked to ensure that new rows satisfy the view-defining condition (that is, the new rows are checked to ensure that they are visible through the view). If they are not, the update will be rejected. If the CHECK OPTION is not specified, INSERT and UPDATE commands on the view are allowed to create rows that are not visible through the view. The following check options are supported:", "LOCAL", "New rows are only checked against the conditions defined directly in the view itself. Any conditions defined on underlying base views are not checked (unless they also specify the CHECK OPTION ).", "CASCADED", "New rows are checked against the conditions of the view and all underlying base views. If the CHECK OPTION is specified, and neither LOCAL nor CASCADED is specified, then CASCADED is assumed.", "The CHECK OPTION may not be used with RECURSIVE views.", "Note that the CHECK OPTION is only supported on views that are automatically updatable, and do not have INSTEAD OF triggers or INSTEAD rules. If an automatically updatable view is defined on top of a base view that has INSTEAD OF triggers, then the LOCAL CHECK OPTION may be used to check the conditions on the automatically updatable view, but the conditions on the base view with INSTEAD OF triggers will not be checked (a cascaded check option will not cascade down to a trigger-updatable view, and any check options defined directly on a trigger-updatable view will be ignored). If the view or any of its base relations has an INSTEAD rule that causes the INSERT or UPDATE command to be rewritten, then all check options will be ignored in the rewritten query, including any checks from automatically updatable views defined on top of the relation with the INSTEAD rule."]}], "signature": "WITH (check_option = value)", "description": ["This parameter may be either local or cascaded , and is equivalent to specifying WITH [ CASCADED | LOCAL ] CHECK OPTION (see below). This option can be changed on existing views using ALTER VIEW ."]}, "14": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "enum"}, {"label": "Values", "value": "local, cascaded"}], "related": [{"url": "/docs/sql/create-view/?v=14", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 14 English manual", "sha256": "ce32f28c1a1e064f26c167a63d68b7d3dd61213f16597c23a377f5c0fcfd3155"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Write checks", "paragraphs": ["This option controls the behavior of automatically updatable views. When this option is specified, INSERT and UPDATE commands on the view will be checked to ensure that new rows satisfy the view-defining condition (that is, the new rows are checked to ensure that they are visible through the view). If they are not, the update will be rejected. If the CHECK OPTION is not specified, INSERT and UPDATE commands on the view are allowed to create rows that are not visible through the view. The following check options are supported:", "LOCAL", "New rows are only checked against the conditions defined directly in the view itself. Any conditions defined on underlying base views are not checked (unless they also specify the CHECK OPTION ).", "CASCADED", "New rows are checked against the conditions of the view and all underlying base views. If the CHECK OPTION is specified, and neither LOCAL nor CASCADED is specified, then CASCADED is assumed.", "The CHECK OPTION may not be used with RECURSIVE views.", "Note that the CHECK OPTION is only supported on views that are automatically updatable, and do not have INSTEAD OF triggers or INSTEAD rules. If an automatically updatable view is defined on top of a base view that has INSTEAD OF triggers, then the LOCAL CHECK OPTION may be used to check the conditions on the automatically updatable view, but the conditions on the base view with INSTEAD OF triggers will not be checked (a cascaded check option will not cascade down to a trigger-updatable view, and any check options defined directly on a trigger-updatable view will be ignored). If the view or any of its base relations has an INSTEAD rule that causes the INSERT or UPDATE command to be rewritten, then all check options will be ignored in the rewritten query, including any checks from automatically updatable views defined on top of the relation with the INSTEAD rule."]}], "signature": "WITH (check_option = value)", "description": ["This parameter may be either local or cascaded , and is equivalent to specifying WITH [ CASCADED | LOCAL ] CHECK OPTION (see below). This option can be changed on existing views using ALTER VIEW ."]}, "15": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "enum"}, {"label": "Values", "value": "local, cascaded"}], "related": [{"url": "/docs/sql/create-view/?v=15", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 15 English manual", "sha256": "5e264be14c16e87295e86ed356aea640f7a46a5a5fe713dc20c903e8301d690c"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Write checks", "paragraphs": ["This option controls the behavior of automatically updatable views. When this option is specified, INSERT and UPDATE commands on the view will be checked to ensure that new rows satisfy the view-defining condition (that is, the new rows are checked to ensure that they are visible through the view). If they are not, the update will be rejected. If the CHECK OPTION is not specified, INSERT and UPDATE commands on the view are allowed to create rows that are not visible through the view. The following check options are supported:", "LOCAL", "New rows are only checked against the conditions defined directly in the view itself. Any conditions defined on underlying base views are not checked (unless they also specify the CHECK OPTION ).", "CASCADED", "New rows are checked against the conditions of the view and all underlying base views. If the CHECK OPTION is specified, and neither LOCAL nor CASCADED is specified, then CASCADED is assumed.", "The CHECK OPTION may not be used with RECURSIVE views.", "Note that the CHECK OPTION is only supported on views that are automatically updatable, and do not have INSTEAD OF triggers or INSTEAD rules. If an automatically updatable view is defined on top of a base view that has INSTEAD OF triggers, then the LOCAL CHECK OPTION may be used to check the conditions on the automatically updatable view, but the conditions on the base view with INSTEAD OF triggers will not be checked (a cascaded check option will not cascade down to a trigger-updatable view, and any check options defined directly on a trigger-updatable view will be ignored). If the view or any of its base relations has an INSTEAD rule that causes the INSERT or UPDATE command to be rewritten, then all check options will be ignored in the rewritten query, including any checks from automatically updatable views defined on top of the relation with the INSTEAD rule."]}], "signature": "WITH (check_option = value)", "description": ["This parameter may be either local or cascaded , and is equivalent to specifying WITH [ CASCADED | LOCAL ] CHECK OPTION (see below)."]}, "16": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "enum"}, {"label": "Values", "value": "local, cascaded"}], "related": [{"url": "/docs/sql/create-view/?v=16", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 16 English manual", "sha256": "4b881ea4898cc76b99becc82db07c4f45d51eb92566127d308b676625b4d06fd"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Write checks", "paragraphs": ["This option controls the behavior of automatically updatable views. When this option is specified, INSERT and UPDATE commands on the view will be checked to ensure that new rows satisfy the view-defining condition (that is, the new rows are checked to ensure that they are visible through the view). If they are not, the update will be rejected. If the CHECK OPTION is not specified, INSERT and UPDATE commands on the view are allowed to create rows that are not visible through the view. The following check options are supported:", "LOCAL", "New rows are only checked against the conditions defined directly in the view itself. Any conditions defined on underlying base views are not checked (unless they also specify the CHECK OPTION ).", "CASCADED", "New rows are checked against the conditions of the view and all underlying base views. If the CHECK OPTION is specified, and neither LOCAL nor CASCADED is specified, then CASCADED is assumed.", "The CHECK OPTION may not be used with RECURSIVE views.", "Note that the CHECK OPTION is only supported on views that are automatically updatable, and do not have INSTEAD OF triggers or INSTEAD rules. If an automatically updatable view is defined on top of a base view that has INSTEAD OF triggers, then the LOCAL CHECK OPTION may be used to check the conditions on the automatically updatable view, but the conditions on the base view with INSTEAD OF triggers will not be checked (a cascaded check option will not cascade down to a trigger-updatable view, and any check options defined directly on a trigger-updatable view will be ignored). If the view or any of its base relations has an INSTEAD rule that causes the INSERT or UPDATE command to be rewritten, then all check options will be ignored in the rewritten query, including any checks from automatically updatable views defined on top of the relation with the INSTEAD rule."]}], "signature": "WITH (check_option = value)", "description": ["This parameter may be either local or cascaded , and is equivalent to specifying WITH [ CASCADED | LOCAL ] CHECK OPTION (see below)."]}, "17": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "enum"}, {"label": "Values", "value": "local, cascaded"}], "related": [{"url": "/docs/sql/create-view/?v=17", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 17 English manual", "sha256": "80b0ff1f7c82a347bb322670817b6cc38c71b249f6b49163dcdd80f3bbd184a4"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Write checks", "paragraphs": ["This option controls the behavior of automatically updatable views. When this option is specified, INSERT , UPDATE , and MERGE commands on the view will be checked to ensure that new rows satisfy the view-defining condition (that is, the new rows are checked to ensure that they are visible through the view). If they are not, the update will be rejected. If the CHECK OPTION is not specified, INSERT , UPDATE , and MERGE commands on the view are allowed to create rows that are not visible through the view. The following check options are supported:", "LOCAL", "New rows are only checked against the conditions defined directly in the view itself. Any conditions defined on underlying base views are not checked (unless they also specify the CHECK OPTION ).", "CASCADED", "New rows are checked against the conditions of the view and all underlying base views. If the CHECK OPTION is specified, and neither LOCAL nor CASCADED is specified, then CASCADED is assumed.", "The CHECK OPTION may not be used with RECURSIVE views.", "Note that the CHECK OPTION is only supported on views that are automatically updatable, and do not have INSTEAD OF triggers or INSTEAD rules. If an automatically updatable view is defined on top of a base view that has INSTEAD OF triggers, then the LOCAL CHECK OPTION may be used to check the conditions on the automatically updatable view, but the conditions on the base view with INSTEAD OF triggers will not be checked (a cascaded check option will not cascade down to a trigger-updatable view, and any check options defined directly on a trigger-updatable view will be ignored). If the view or any of its base relations has an INSTEAD rule that causes the INSERT or UPDATE command to be rewritten, then all check options will be ignored in the rewritten query, including any checks from automatically updatable views defined on top of the relation with the INSTEAD rule. MERGE is not supported if the view or any of its base relations have rules."]}], "signature": "WITH (check_option = value)", "description": ["This parameter may be either local or cascaded , and is equivalent to specifying WITH [ CASCADED | LOCAL ] CHECK OPTION (see below)."]}, "18": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "enum"}, {"label": "Values", "value": "local, cascaded"}], "related": [{"url": "/docs/sql/create-view/?v=18", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 18 English manual", "sha256": "0c11551250a39c2136437e8cded6bcb5bb8d324fa60b9b2e86b2276ad60ee599"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Write checks", "paragraphs": ["This option controls the behavior of automatically updatable views. When this option is specified, INSERT , UPDATE , and MERGE commands on the view will be checked to ensure that new rows satisfy the view-defining condition (that is, the new rows are checked to ensure that they are visible through the view). If they are not, the update will be rejected. If the CHECK OPTION is not specified, INSERT , UPDATE , and MERGE commands on the view are allowed to create rows that are not visible through the view. The following check options are supported:", "LOCAL", "New rows are only checked against the conditions defined directly in the view itself. Any conditions defined on underlying base views are not checked (unless they also specify the CHECK OPTION ).", "CASCADED", "New rows are checked against the conditions of the view and all underlying base views. If the CHECK OPTION is specified, and neither LOCAL nor CASCADED is specified, then CASCADED is assumed.", "The CHECK OPTION may not be used with RECURSIVE views.", "Note that the CHECK OPTION is only supported on views that are automatically updatable, and do not have INSTEAD OF triggers or INSTEAD rules. If an automatically updatable view is defined on top of a base view that has INSTEAD OF triggers, then the LOCAL CHECK OPTION may be used to check the conditions on the automatically updatable view, but the conditions on the base view with INSTEAD OF triggers will not be checked (a cascaded check option will not cascade down to a trigger-updatable view, and any check options defined directly on a trigger-updatable view will be ignored). If the view or any of its base relations has an INSTEAD rule that causes the INSERT or UPDATE command to be rewritten, then all check options will be ignored in the rewritten query, including any checks from automatically updatable views defined on top of the relation with the INSTEAD rule. MERGE is not supported if the view or any of its base relations have rules."]}], "signature": "WITH (check_option = value)", "description": ["This parameter may be either local or cascaded , and is equivalent to specifying WITH [ CASCADED | LOCAL ] CHECK OPTION (see below)."]}, "19": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "enum"}, {"label": "Values", "value": "local, cascaded"}], "related": [{"url": "/docs/sql/create-view/?v=19", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 19 English manual", "sha256": "eb32d7fd0cdf4f868af1a1a1c866aabe70295e50e327b97c9577a944a6092a79"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Write checks", "paragraphs": ["This option controls the behavior of automatically updatable views. When this option is specified, INSERT , UPDATE , and MERGE commands on the view will be checked to ensure that new rows satisfy the view-defining condition (that is, the new rows are checked to ensure that they are visible through the view). If they are not, the update will be rejected. If the CHECK OPTION is not specified, INSERT , UPDATE , and MERGE commands on the view are allowed to create rows that are not visible through the view. The following check options are supported:", "LOCAL", "New rows are only checked against the conditions defined directly in the view itself. Any conditions defined on underlying base views are not checked (unless they also specify the CHECK OPTION ).", "CASCADED", "New rows are checked against the conditions of the view and all underlying base views. If the CHECK OPTION is specified, and neither LOCAL nor CASCADED is specified, then CASCADED is assumed.", "The CHECK OPTION may not be used with RECURSIVE views.", "Note that the CHECK OPTION is only supported on views that are automatically updatable, and do not have INSTEAD OF triggers or INSTEAD rules. If an automatically updatable view is defined on top of a base view that has INSTEAD OF triggers, then the LOCAL CHECK OPTION may be used to check the conditions on the automatically updatable view, but the conditions on the base view with INSTEAD OF triggers will not be checked (a cascaded check option will not cascade down to a trigger-updatable view, and any check options defined directly on a trigger-updatable view will be ignored). If the view or any of its base relations has an INSTEAD rule that causes the INSERT or UPDATE command to be rewritten, then all check options will be ignored in the rewritten query, including any checks from automatically updatable views defined on top of the relation with the INSTEAD rule. MERGE is not supported if the view or any of its base relations have rules."]}], "signature": "WITH (check_option = value)", "description": ["This parameter may be either local or cascaded , and is equivalent to specifying WITH [ CASCADED | LOCAL ] CHECK OPTION (see below)."]}, "20": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "enum"}, {"label": "Values", "value": "local, cascaded"}], "related": [{"url": "/docs/sql/create-view/?v=20", "label": "CREATE VIEW"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 20 English manual", "sha256": "ab4714c547b7e5dc1c3730b0702032f40e58945b0078a5ea5de9f8644c1154ee"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Write checks", "paragraphs": ["This option controls the behavior of automatically updatable views. When this option is specified, INSERT , UPDATE , and MERGE commands on the view will be checked to ensure that new rows satisfy the view-defining condition (that is, the new rows are checked to ensure that they are visible through the view). If they are not, the update will be rejected. If the CHECK OPTION is not specified, INSERT , UPDATE , and MERGE commands on the view are allowed to create rows that are not visible through the view. The following check options are supported:", "LOCAL", "New rows are only checked against the conditions defined directly in the view itself. Any conditions defined on underlying base views are not checked (unless they also specify the CHECK OPTION ).", "CASCADED", "New rows are checked against the conditions of the view and all underlying base views. If the CHECK OPTION is specified, and neither LOCAL nor CASCADED is specified, then CASCADED is assumed.", "The CHECK OPTION may not be used with RECURSIVE views.", "Note that the CHECK OPTION is only supported on views that are automatically updatable, and do not have INSTEAD OF triggers or INSTEAD rules. If an automatically updatable view is defined on top of a base view that has INSTEAD OF triggers, then the LOCAL CHECK OPTION may be used to check the conditions on the automatically updatable view, but the conditions on the base view with INSTEAD OF triggers will not be checked (a cascaded check option will not cascade down to a trigger-updatable view, and any check options defined directly on a trigger-updatable view will be ignored). If the view or any of its base relations has an INSTEAD rule that causes the INSERT or UPDATE command to be rewritten, then all check options will be ignored in the rewritten query, including any checks from automatically updatable views defined on top of the relation with the INSTEAD rule. MERGE is not supported if the view or any of its base relations have rules."]}], "signature": "WITH (check_option = value)", "description": ["This parameter may be either local or cascaded , and is equivalent to specifying WITH [ CASCADED | LOCAL ] CHECK OPTION (see below)."]}}, "content_hash": "3d459c165d059d881095bfc4bfdb23645b5d9cf14ebb57933008bf14291b1569", "imported_at": "2026-09-27T09:57:59.033", "url": "/wiki/relopts/view-check-option/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/view-check-option/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/view-check-option/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/view-check-option/?v=12"}, {"major": "13", "state": "changed", "label": "Interface or attribute change", "title": "PostgreSQL 13.23 \u00b7 Interface or attribute change", "url": "/wiki/relopts/view-check-option/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/view-check-option/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/view-check-option/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/view-check-option/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/view-check-option/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/view-check-option/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/view-check-option/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/view-check-option/?v=20"}], "present": true}, {"slug": "view-security-barrier", "name": "security_barrier", "name_zh": "security_barrier", "category": "View options", "summary": "This should be used if the view is intended to provide row-level security. See Section 39.5 for full details.", "aliases": ["view.security_barrier"], "versions": {"10": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-view/?v=10", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 10.23", "label": "10.23", "major": "10", "channel": "historical", "revision": "4ff6f6193d91bf44fc701f657cc3295850bf786e42eafbfeed9f4879c3522613"}, "sources": [{"url": "/docs/10/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 10 English manual", "sha256": "f3beb72fc3c516331a0c0535d13aa59329eb7fdc265b20945dc7a37b97cfed4a"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Security semantics", "paragraphs": ["If an automatically updatable view is marked with the security_barrier property then all the view's WHERE conditions (and any conditions using operators which are marked as LEAKPROOF ) will always be evaluated before any conditions that a user of the view has added. See Section 40.5 for full details. Note that, due to this, rows which are not ultimately returned (because they do not pass the user's WHERE conditions) may still end up being locked. EXPLAIN can be used to see which conditions are applied at the relation level (and therefore do not lock rows) and which are not."]}], "signature": "WITH (security_barrier = value)", "description": ["This should be used if the view is intended to provide row-level security. See Section 40.5 for full details."]}, "11": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-view/?v=11", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 11.22", "label": "11.22", "major": "11", "channel": "historical", "revision": "284f2186559443efefbb1ea3b00740c25dccd01e540ecbdb81dadf5127e54a0b"}, "sources": [{"url": "/docs/11/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 11 English manual", "sha256": "cb691ccbc81965b50e4404c037e081b1038886bed54a2da7ed28d083ff11becd"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Security semantics", "paragraphs": ["If an automatically updatable view is marked with the security_barrier property then all the view's WHERE conditions (and any conditions using operators which are marked as LEAKPROOF ) will always be evaluated before any conditions that a user of the view has added. See Section 41.5 for full details. Note that, due to this, rows which are not ultimately returned (because they do not pass the user's WHERE conditions) may still end up being locked. EXPLAIN can be used to see which conditions are applied at the relation level (and therefore do not lock rows) and which are not."]}], "signature": "WITH (security_barrier = value)", "description": ["This should be used if the view is intended to provide row-level security. See Section 41.5 for full details."]}, "12": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-view/?v=12", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 12.22", "label": "12.22", "major": "12", "channel": "historical", "revision": "0a1032bc0c23478646e9ee7d36edb066dca27b8540fd64d7fd47dcb6a8a6ccb4"}, "sources": [{"url": "/docs/12/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 12 English manual", "sha256": "30c56ff14a8865b60f2954e70821eb7a6187fb35c2140b4c5697894b6f24bc9e"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Security semantics", "paragraphs": ["If an automatically updatable view is marked with the security_barrier property then all the view's WHERE conditions (and any conditions using operators which are marked as LEAKPROOF ) will always be evaluated before any conditions that a user of the view has added. See Section 40.5 for full details. Note that, due to this, rows which are not ultimately returned (because they do not pass the user's WHERE conditions) may still end up being locked. EXPLAIN can be used to see which conditions are applied at the relation level (and therefore do not lock rows) and which are not."]}], "signature": "WITH (security_barrier = value)", "description": ["This should be used if the view is intended to provide row-level security. See Section 40.5 for full details."]}, "13": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-view/?v=13", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 13.23", "label": "13.23", "major": "13", "channel": "historical", "revision": "346825c2d5fbebb2bd997afbb2d49edfd782dce050c0b934e84a883e5446a99f"}, "sources": [{"url": "/docs/13/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 13 English manual", "sha256": "99ec0fd97653a0486c7d2575acc9713f73e2a9b12464e4dfa0b2046e772fd111"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Security semantics", "paragraphs": ["If an automatically updatable view is marked with the security_barrier property then all the view's WHERE conditions (and any conditions using operators which are marked as LEAKPROOF ) will always be evaluated before any conditions that a user of the view has added. See Section 40.5 for full details. Note that, due to this, rows which are not ultimately returned (because they do not pass the user's WHERE conditions) may still end up being locked. EXPLAIN can be used to see which conditions are applied at the relation level (and therefore do not lock rows) and which are not."]}], "signature": "WITH (security_barrier = value)", "description": ["This should be used if the view is intended to provide row-level security. See Section 40.5 for full details."]}, "14": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-view/?v=14", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 14.24", "label": "14.24", "major": "14", "channel": "stable", "revision": "b6e7ed6d017bf1d63aae215156cde763babd657199df9fa10123733290c31260"}, "sources": [{"url": "/docs/14/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 14 English manual", "sha256": "ce32f28c1a1e064f26c167a63d68b7d3dd61213f16597c23a377f5c0fcfd3155"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Security semantics", "paragraphs": ["If an automatically updatable view is marked with the security_barrier property then all the view's WHERE conditions (and any conditions using operators which are marked as LEAKPROOF ) will always be evaluated before any conditions that a user of the view has added. See Section 41.5 for full details. Note that, due to this, rows which are not ultimately returned (because they do not pass the user's WHERE conditions) may still end up being locked. EXPLAIN can be used to see which conditions are applied at the relation level (and therefore do not lock rows) and which are not."]}], "signature": "WITH (security_barrier = value)", "description": ["This should be used if the view is intended to provide row-level security. See Section 41.5 for full details."]}, "15": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-view/?v=15", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 15 English manual", "sha256": "5e264be14c16e87295e86ed356aea640f7a46a5a5fe713dc20c903e8301d690c"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Security semantics", "paragraphs": ["If an automatically updatable view is marked with the security_barrier property then all the view's WHERE conditions (and any conditions using operators which are marked as LEAKPROOF ) will always be evaluated before any conditions that a user of the view has added. See Section 41.5 for full details. Note that, due to this, rows which are not ultimately returned (because they do not pass the user's WHERE conditions) may still end up being locked. EXPLAIN can be used to see which conditions are applied at the relation level (and therefore do not lock rows) and which are not."]}], "signature": "WITH (security_barrier = value)", "description": ["This should be used if the view is intended to provide row-level security. See Section 41.5 for full details."]}, "16": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-view/?v=16", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 16 English manual", "sha256": "4b881ea4898cc76b99becc82db07c4f45d51eb92566127d308b676625b4d06fd"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Security semantics", "paragraphs": ["If an automatically updatable view is marked with the security_barrier property then all the view's WHERE conditions (and any conditions using operators which are marked as LEAKPROOF ) will always be evaluated before any conditions that a user of the view has added. See Section 41.5 for full details. Note that, due to this, rows which are not ultimately returned (because they do not pass the user's WHERE conditions) may still end up being locked. EXPLAIN can be used to see which conditions are applied at the relation level (and therefore do not lock rows) and which are not."]}], "signature": "WITH (security_barrier = value)", "description": ["This should be used if the view is intended to provide row-level security. See Section 41.5 for full details."]}, "17": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-view/?v=17", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 17 English manual", "sha256": "80b0ff1f7c82a347bb322670817b6cc38c71b249f6b49163dcdd80f3bbd184a4"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Security semantics", "paragraphs": ["If an automatically updatable view is marked with the security_barrier property then all the view's WHERE conditions (and any conditions using operators which are marked as LEAKPROOF ) will always be evaluated before any conditions that a user of the view has added. See Section 39.5 for full details. Note that, due to this, rows which are not ultimately returned (because they do not pass the user's WHERE conditions) may still end up being locked. EXPLAIN can be used to see which conditions are applied at the relation level (and therefore do not lock rows) and which are not."]}], "signature": "WITH (security_barrier = value)", "description": ["This should be used if the view is intended to provide row-level security. See Section 39.5 for full details."]}, "18": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-view/?v=18", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 18 English manual", "sha256": "0c11551250a39c2136437e8cded6bcb5bb8d324fa60b9b2e86b2276ad60ee599"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Security semantics", "paragraphs": ["If an automatically updatable view is marked with the security_barrier property then all the view's WHERE conditions (and any conditions using operators which are marked as LEAKPROOF ) will always be evaluated before any conditions that a user of the view has added. See Section 39.5 for full details. Note that, due to this, rows which are not ultimately returned (because they do not pass the user's WHERE conditions) may still end up being locked. EXPLAIN can be used to see which conditions are applied at the relation level (and therefore do not lock rows) and which are not."]}], "signature": "WITH (security_barrier = value)", "description": ["This should be used if the view is intended to provide row-level security. See Section 39.5 for full details."]}, "19": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-view/?v=19", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 19 English manual", "sha256": "eb32d7fd0cdf4f868af1a1a1c866aabe70295e50e327b97c9577a944a6092a79"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Security semantics", "paragraphs": ["If an automatically updatable view is marked with the security_barrier property then all the view's WHERE conditions (and any conditions using operators which are marked as LEAKPROOF ) will always be evaluated before any conditions that a user of the view has added. See Section 39.5 for full details. Note that, due to this, rows which are not ultimately returned (because they do not pass the user's WHERE conditions) may still end up being locked. EXPLAIN can be used to see which conditions are applied at the relation level (and therefore do not lock rows) and which are not."]}], "signature": "WITH (security_barrier = value)", "description": ["This should be used if the view is intended to provide row-level security. See Section 39.5 for full details."]}, "20": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-view/?v=20", "label": "CREATE VIEW"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 20 English manual", "sha256": "ab4714c547b7e5dc1c3730b0702032f40e58945b0078a5ea5de9f8644c1154ee"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Security semantics", "paragraphs": ["If an automatically updatable view is marked with the security_barrier property then all the view's WHERE conditions (and any conditions using operators which are marked as LEAKPROOF ) will always be evaluated before any conditions that a user of the view has added. See Section 39.5 for full details. Note that, due to this, rows which are not ultimately returned (because they do not pass the user's WHERE conditions) may still end up being locked. EXPLAIN can be used to see which conditions are applied at the relation level (and therefore do not lock rows) and which are not."]}], "signature": "WITH (security_barrier = value)", "description": ["This should be used if the view is intended to provide row-level security. See Section 39.5 for full details."]}}, "content_hash": "5db22005bb39a4f721f6ec732ca2b40c1a41055755991be7ed5acc9641a0c910", "imported_at": "2026-09-27T09:57:59.035", "url": "/wiki/relopts/view-security-barrier/?v=18", "cells": [{"major": "10", "state": "present", "label": "Recorded", "title": "PostgreSQL 10.23 \u00b7 Recorded", "url": "/wiki/relopts/view-security-barrier/?v=10"}, {"major": "11", "state": "present", "label": "Recorded", "title": "PostgreSQL 11.22 \u00b7 Recorded", "url": "/wiki/relopts/view-security-barrier/?v=11"}, {"major": "12", "state": "present", "label": "Recorded", "title": "PostgreSQL 12.22 \u00b7 Recorded", "url": "/wiki/relopts/view-security-barrier/?v=12"}, {"major": "13", "state": "present", "label": "Recorded", "title": "PostgreSQL 13.23 \u00b7 Recorded", "url": "/wiki/relopts/view-security-barrier/?v=13"}, {"major": "14", "state": "present", "label": "Recorded", "title": "PostgreSQL 14.24 \u00b7 Recorded", "url": "/wiki/relopts/view-security-barrier/?v=14"}, {"major": "15", "state": "present", "label": "Recorded", "title": "PostgreSQL 15.19 \u00b7 Recorded", "url": "/wiki/relopts/view-security-barrier/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/view-security-barrier/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/view-security-barrier/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/view-security-barrier/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/view-security-barrier/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/view-security-barrier/?v=20"}], "present": true}, {"slug": "view-security-invoker", "name": "security_invoker", "name_zh": "security_invoker", "category": "View options", "summary": "This option causes the underlying base relations to be checked against the privileges of the user of the view rather than the view owner. See the notes below for full details.", "aliases": ["view.security_invoker"], "versions": {"15": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-view/?v=15", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 15.19", "label": "15.19", "major": "15", "channel": "stable", "revision": "643ecd492fa284d4d55861f15cbd7c0c7451abce96c8d56485bb2729caba37d5"}, "sources": [{"url": "/docs/15/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 15 English manual", "sha256": "5e264be14c16e87295e86ed356aea640f7a46a5a5fe713dc20c903e8301d690c"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Security semantics", "paragraphs": ["If the view has the security_invoker property set to true , access to the underlying base relations is determined by the permissions of the user executing the query, rather than the view owner. Thus, the user of a security invoker view must have the relevant permissions on the view and its underlying base relations.", "If any of the underlying base relations is a security invoker view, it will be treated as if it had been accessed directly from the original query. Thus, a security invoker view will always check its underlying base relations using the permissions of the current user, even if it is accessed from a view without the security_invoker property.", "If any of the underlying base relations has row-level security enabled, then by default, the row-level security policies of the view owner are applied, and access to any additional relations referred to by those policies is determined by the permissions of the view owner. However, if the view has security_invoker set to true , then the policies and permissions of the invoking user are used instead, as if the base relations had been referenced directly from the query using the view.", "Functions called in the view are treated the same as if they had been called directly from the query using the view. Therefore, the user of a view must have permissions to call all functions used by the view. Functions in the view are executed with the privileges of the user executing the query or the function owner, depending on whether the functions are defined as SECURITY INVOKER or SECURITY DEFINER . Thus, for example, calling CURRENT_USER directly in a view will always return the invoking user, not the view owner. This is not affected by the view's security_invoker setting, and so a view with security_invoker set to false is not equivalent to a SECURITY DEFINER function and those concepts should not be confused.", "Note that the user performing the insert, update or delete on the view must have the corresponding insert, update or delete privilege on the view. In addition, by default, the view's owner must have the relevant privileges on the underlying base relations, whereas the user performing the update does not need any permissions on the underlying base relations (see Section 41.5 ). However, if the view has security_invoker set to true , the user performing the update, rather than the view owner, must have the relevant privileges on the underlying base relations."]}], "signature": "WITH (security_invoker = value)", "description": ["This option causes the underlying base relations to be checked against the privileges of the user of the view rather than the view owner. See the notes below for full details."]}, "16": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-view/?v=16", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 16.15", "label": "16.15", "major": "16", "channel": "stable", "revision": "0080d7d37081f27216dc4aa4f6ad85ea24c0c0441e702e6d0b190a339fd76f62"}, "sources": [{"url": "/docs/16/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 16 English manual", "sha256": "4b881ea4898cc76b99becc82db07c4f45d51eb92566127d308b676625b4d06fd"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Security semantics", "paragraphs": ["If the view has the security_invoker property set to true , access to the underlying base relations is determined by the permissions of the user executing the query, rather than the view owner. Thus, the user of a security invoker view must have the relevant permissions on the view and its underlying base relations.", "If any of the underlying base relations is a security invoker view, it will be treated as if it had been accessed directly from the original query. Thus, a security invoker view will always check its underlying base relations using the permissions of the current user, even if it is accessed from a view without the security_invoker property.", "If any of the underlying base relations has row-level security enabled, then by default, the row-level security policies of the view owner are applied, and access to any additional relations referred to by those policies is determined by the permissions of the view owner. However, if the view has security_invoker set to true , then the policies and permissions of the invoking user are used instead, as if the base relations had been referenced directly from the query using the view.", "Functions called in the view are treated the same as if they had been called directly from the query using the view. Therefore, the user of a view must have permissions to call all functions used by the view. Functions in the view are executed with the privileges of the user executing the query or the function owner, depending on whether the functions are defined as SECURITY INVOKER or SECURITY DEFINER . Thus, for example, calling CURRENT_USER directly in a view will always return the invoking user, not the view owner. This is not affected by the view's security_invoker setting, and so a view with security_invoker set to false is not equivalent to a SECURITY DEFINER function and those concepts should not be confused.", "Note that the user performing the insert, update or delete on the view must have the corresponding insert, update or delete privilege on the view. In addition, by default, the view's owner must have the relevant privileges on the underlying base relations, whereas the user performing the update does not need any permissions on the underlying base relations (see Section 41.5 ). However, if the view has security_invoker set to true , the user performing the update, rather than the view owner, must have the relevant privileges on the underlying base relations."]}], "signature": "WITH (security_invoker = value)", "description": ["This option causes the underlying base relations to be checked against the privileges of the user of the view rather than the view owner. See the notes below for full details."]}, "17": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-view/?v=17", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 17.11", "label": "17.11", "major": "17", "channel": "stable", "revision": "440f894c3464e7cb4fedc9846b948ca21cd2ffcef1697ff56a28eb641ee7c3d8"}, "sources": [{"url": "/docs/17/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 17 English manual", "sha256": "80b0ff1f7c82a347bb322670817b6cc38c71b249f6b49163dcdd80f3bbd184a4"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Security semantics", "paragraphs": ["If the view has the security_invoker property set to true , access to the underlying base relations is determined by the permissions of the user executing the query, rather than the view owner. Thus, the user of a security invoker view must have the relevant permissions on the view and its underlying base relations.", "If any of the underlying base relations is a security invoker view, it will be treated as if it had been accessed directly from the original query. Thus, a security invoker view will always check its underlying base relations using the permissions of the current user, even if it is accessed from a view without the security_invoker property.", "If any of the underlying base relations has row-level security enabled, then by default, the row-level security policies of the view owner are applied, and access to any additional relations referred to by those policies is determined by the permissions of the view owner. However, if the view has security_invoker set to true , then the policies and permissions of the invoking user are used instead, as if the base relations had been referenced directly from the query using the view.", "Functions called in the view are treated the same as if they had been called directly from the query using the view. Therefore, the user of a view must have permissions to call all functions used by the view. Functions in the view are executed with the privileges of the user executing the query or the function owner, depending on whether the functions are defined as SECURITY INVOKER or SECURITY DEFINER . Thus, for example, calling CURRENT_USER directly in a view will always return the invoking user, not the view owner. This is not affected by the view's security_invoker setting, and so a view with security_invoker set to false is not equivalent to a SECURITY DEFINER function and those concepts should not be confused.", "Note that the user performing the insert, update or delete on the view must have the corresponding insert, update or delete privilege on the view. In addition, by default, the view's owner must have the relevant privileges on the underlying base relations, whereas the user performing the update does not need any permissions on the underlying base relations (see Section 39.5 ). However, if the view has security_invoker set to true , the user performing the update, rather than the view owner, must have the relevant privileges on the underlying base relations."]}], "signature": "WITH (security_invoker = value)", "description": ["This option causes the underlying base relations to be checked against the privileges of the user of the view rather than the view owner. See the notes below for full details."]}, "18": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-view/?v=18", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 18.6", "label": "18.6", "major": "18", "channel": "stable", "revision": "eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"}, "sources": [{"url": "/docs/18/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 18 English manual", "sha256": "0c11551250a39c2136437e8cded6bcb5bb8d324fa60b9b2e86b2276ad60ee599"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Security semantics", "paragraphs": ["If the view has the security_invoker property set to true , access to the underlying base relations is determined by the permissions of the user executing the query, rather than the view owner. Thus, the user of a security invoker view must have the relevant permissions on the view and its underlying base relations.", "If any of the underlying base relations is a security invoker view, it will be treated as if it had been accessed directly from the original query. Thus, a security invoker view will always check its underlying base relations using the permissions of the current user, even if it is accessed from a view without the security_invoker property.", "If any of the underlying base relations has row-level security enabled, then by default, the row-level security policies of the view owner are applied, and access to any additional relations referred to by those policies is determined by the permissions of the view owner. However, if the view has security_invoker set to true , then the policies and permissions of the invoking user are used instead, as if the base relations had been referenced directly from the query using the view.", "Functions called in the view are treated the same as if they had been called directly from the query using the view. Therefore, the user of a view must have permissions to call all functions used by the view. Functions in the view are executed with the privileges of the user executing the query or the function owner, depending on whether the functions are defined as SECURITY INVOKER or SECURITY DEFINER . Thus, for example, calling CURRENT_USER directly in a view will always return the invoking user, not the view owner. This is not affected by the view's security_invoker setting, and so a view with security_invoker set to false is not equivalent to a SECURITY DEFINER function and those concepts should not be confused.", "Note that the user performing the insert, update or delete on the view must have the corresponding insert, update or delete privilege on the view. In addition, by default, the view's owner must have the relevant privileges on the underlying base relations, whereas the user performing the update does not need any permissions on the underlying base relations (see Section 39.5 ). However, if the view has security_invoker set to true , the user performing the update, rather than the view owner, must have the relevant privileges on the underlying base relations."]}], "signature": "WITH (security_invoker = value)", "description": ["This option causes the underlying base relations to be checked against the privileges of the user of the view rather than the view owner. See the notes below for full details."]}, "19": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-view/?v=19", "label": "CREATE VIEW"}], "release": {"ref": "Local English manual 19 beta 4", "label": "19 beta 4", "major": "19", "channel": "preview", "revision": "df6d20830d1a09734a2db6ffc3a6138ce80e669294e56a30f6b5d4a89d81aef1"}, "sources": [{"url": "/docs/19/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 19 English manual", "sha256": "eb32d7fd0cdf4f868af1a1a1c866aabe70295e50e327b97c9577a944a6092a79"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Security semantics", "paragraphs": ["If the view has the security_invoker property set to true , access to the underlying base relations is determined by the permissions of the user executing the query, rather than the view owner. Thus, the user of a security invoker view must have the relevant permissions on the view and its underlying base relations.", "If any of the underlying base relations is a security invoker view, it will be treated as if it had been accessed directly from the original query. Thus, a security invoker view will always check its underlying base relations using the permissions of the current user, even if it is accessed from a view without the security_invoker property.", "If any of the underlying base relations has row-level security enabled, then by default, the row-level security policies of the view owner are applied, and access to any additional relations referred to by those policies is determined by the permissions of the view owner. However, if the view has security_invoker set to true , then the policies and permissions of the invoking user are used instead, as if the base relations had been referenced directly from the query using the view.", "Functions called in the view are treated the same as if they had been called directly from the query using the view. Therefore, the user of a view must have permissions to call all functions used by the view. Functions in the view are executed with the privileges of the user executing the query or the function owner, depending on whether the functions are defined as SECURITY INVOKER or SECURITY DEFINER . Thus, for example, calling CURRENT_USER directly in a view will always return the invoking user, not the view owner. This is not affected by the view's security_invoker setting, and so a view with security_invoker set to false is not equivalent to a SECURITY DEFINER function and those concepts should not be confused.", "Note that the user performing the insert, update or delete on the view must have the corresponding insert, update or delete privilege on the view. In addition, by default, the view's owner must have the relevant privileges on the underlying base relations, whereas the user performing the update does not need any permissions on the underlying base relations (see Section 39.5 ). However, if the view has security_invoker set to true , the user performing the update, rather than the view owner, must have the relevant privileges on the underlying base relations."]}], "signature": "WITH (security_invoker = value)", "description": ["This option causes the underlying base relations to be checked against the privileges of the user of the view rather than the view owner. See the notes below for full details."]}, "20": {"facts": [{"label": "Applies to", "value": "View options"}, {"label": "Value type", "value": "boolean"}], "related": [{"url": "/docs/sql/create-view/?v=20", "label": "CREATE VIEW"}], "release": {"ref": "2c10c2ce4d7bcd57543a49ab402af02a39724e0a", "label": "20 devel", "major": "20", "channel": "devel", "revision": "ca199fbaaf6c4bd29cd5a98beaf34d9f4141c15d2f94d1d0202f3204ef18d09f"}, "sources": [{"url": "/docs/devel/sql-createview.html", "path": "sql-createview.html", "label": "PostgreSQL 20 English manual", "sha256": "ab4714c547b7e5dc1c3730b0702032f40e58945b0078a5ea5de9f8644c1154ee"}], "sections": [{"title": "View options", "paragraphs": ["Views do not store query results. Set these security or update semantics with CREATE VIEW WITH or ALTER VIEW."]}, {"title": "Security semantics", "paragraphs": ["If the view has the security_invoker property set to true , access to the underlying base relations is determined by the permissions of the user executing the query, rather than the view owner. Thus, the user of a security invoker view must have the relevant permissions on the view and its underlying base relations.", "If any of the underlying base relations is a security invoker view, it will be treated as if it had been accessed directly from the original query. Thus, a security invoker view will always check its underlying base relations using the permissions of the current user, even if it is accessed from a view without the security_invoker property.", "If any of the underlying base relations has row-level security enabled, then by default, the row-level security policies of the view owner are applied, and access to any additional relations referred to by those policies is determined by the permissions of the view owner. However, if the view has security_invoker set to true , then the policies and permissions of the invoking user are used instead, as if the base relations had been referenced directly from the query using the view.", "Functions called in the view are treated the same as if they had been called directly from the query using the view. Therefore, the user of a view must have permissions to call all functions used by the view. Functions in the view are executed with the privileges of the user executing the query or the function owner, depending on whether the functions are defined as SECURITY INVOKER or SECURITY DEFINER . Thus, for example, calling CURRENT_USER directly in a view will always return the invoking user, not the view owner. This is not affected by the view's security_invoker setting, and so a view with security_invoker set to false is not equivalent to a SECURITY DEFINER function and those concepts should not be confused.", "Note that the user performing the insert, update or delete on the view must have the corresponding insert, update or delete privilege on the view. In addition, by default, the view's owner must have the relevant privileges on the underlying base relations, whereas the user performing the update does not need any permissions on the underlying base relations (see Section 39.5 ). However, if the view has security_invoker set to true , the user performing the update, rather than the view owner, must have the relevant privileges on the underlying base relations."]}], "signature": "WITH (security_invoker = value)", "description": ["This option causes the underlying base relations to be checked against the privileges of the user of the view rather than the view owner. See the notes below for full details."]}}, "content_hash": "222e2bddb87cde75bfbe3845d01d21f69886ec6e9ca1dc730e6fe80ef9c65c7c", "imported_at": "2026-09-27T09:57:59.037", "url": "/wiki/relopts/view-security-invoker/?v=18", "cells": [{"major": "10", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 10.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/view-security-invoker/?v=10"}, {"major": "11", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 11.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/view-security-invoker/?v=11"}, {"major": "12", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 12.22 \u00b7 Not recorded in this version", "url": "/wiki/relopts/view-security-invoker/?v=12"}, {"major": "13", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 13.23 \u00b7 Not recorded in this version", "url": "/wiki/relopts/view-security-invoker/?v=13"}, {"major": "14", "state": "absent", "label": "Not recorded in this version", "title": "PostgreSQL 14.24 \u00b7 Not recorded in this version", "url": "/wiki/relopts/view-security-invoker/?v=14"}, {"major": "15", "state": "added", "label": "First recorded in this sample", "title": "PostgreSQL 15.19 \u00b7 First recorded in this sample", "url": "/wiki/relopts/view-security-invoker/?v=15"}, {"major": "16", "state": "present", "label": "Recorded", "title": "PostgreSQL 16.15 \u00b7 Recorded", "url": "/wiki/relopts/view-security-invoker/?v=16"}, {"major": "17", "state": "present", "label": "Recorded", "title": "PostgreSQL 17.11 \u00b7 Recorded", "url": "/wiki/relopts/view-security-invoker/?v=17"}, {"major": "18", "state": "present", "label": "Recorded", "title": "PostgreSQL 18.6 \u00b7 Recorded", "url": "/wiki/relopts/view-security-invoker/?v=18"}, {"major": "19", "state": "present", "label": "Recorded", "title": "PostgreSQL 19 beta 4 \u00b7 Recorded", "url": "/wiki/relopts/view-security-invoker/?v=19"}, {"major": "20", "state": "present", "label": "Recorded", "title": "PostgreSQL 20 devel \u00b7 Recorded", "url": "/wiki/relopts/view-security-invoker/?v=20"}], "present": true}], "total": 60, "present": 56, "collection_tables": []}