From df7cc3976db6980d115d1dc6556f021d9783d579 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Tue, 7 Jun 2016 14:15:42 -0400 Subject: [PATCH] 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. --- doc/src/sgml/catalogs.sgml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml index eac6671e7a..7dc7d1ff7b 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, CREATE + are normally SQL commands to do that. (For example, CREATE DATABASE inserts a row into the pg_database catalog — 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.