database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-03 22:24:49 +03:00
Code

doc: Update wording about direct system catalog manipulation

Browse Source 
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.
This commit is contained in:
Peter Eisentraut 2016-06-07 14:15:42 -04:00
parent 79616ae73b
commit df7cc3976d
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/src/sgml/catalogs.sgml
View File

@ -14,11 +14,13 @@
tables. You can drop and recreate the tables, add columns, insert tables. You can drop and recreate the tables, add columns, insert
and update values, and severely mess up your system that way. and update values, and severely mess up your system that way.
Normally, one should not change the system catalogs by hand, there 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 DATABASE</command> inserts a row into the
<structname>pg_database</structname> catalog &mdash; and actually <structname>pg_database</structname> catalog &mdash; and actually
creates the database on disk.) There are some exceptions for 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> </para>
<sect1 id="catalogs-overview"> <sect1 id="catalogs-overview">