aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2016-06-07 14:15:42 -0400
committerPeter Eisentraut <peter_e@gmx.net>2016-06-07 14:18:55 -0400
commitdf7cc3976db6980d115d1dc6556f021d9783d579 (patch)
treed35de18df80fbe1b7b9b722bc64638cea0eb999e
parent79616ae73b0ba2fb650a9d8ebc5ce8a088cb3858 (diff)
downloadpostgresql-df7cc3976db6980d115d1dc6556f021d9783d579.tar.gz
postgresql-df7cc3976db6980d115d1dc6556f021d9783d579.zip
doc: Update wording about direct system catalog manipulation
It was previously suggested that "esoteric" operations such as creating a new access method would require direct manipulation of the system catalogs, but that example has gone away, and I can't think of a new one to replace it, so just put in some weasel wording.
-rw-r--r--doc/src/sgml/catalogs.sgml6
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml
index eac6671e7a2..7dc7d1ff7b6 100644
--- a/doc/src/sgml/catalogs.sgml
+++ b/doc/src/sgml/catalogs.sgml
@@ -14,11 +14,13 @@
tables. You can drop and recreate the tables, add columns, insert
and update values, and severely mess up your system that way.
Normally, one should not change the system catalogs by hand, there
- are always SQL commands to do that. (For example, <command>CREATE
+ are normally SQL commands to do that. (For example, <command>CREATE
DATABASE</command> inserts a row into the
<structname>pg_database</structname> catalog &mdash; and actually
creates the database on disk.) There are some exceptions for
- particularly esoteric operations, such as adding index access methods.
+ particularly esoteric operations, but many of those have been made
+ available as SQL commands over time, and so the need for direct manipulation
+ of the system catalogs is ever decreasing.
</para>
<sect1 id="catalogs-overview">