Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitdf7cc39

Browse files
committed
doc: Update wording about direct system catalog manipulation
It was previously suggested that "esoteric" operations such as creatinga new access method would require direct manipulation of the systemcatalogs, but that example has gone away, and I can't think of a new oneto replace it, so just put in some weasel wording.
1 parent79616ae commitdf7cc39

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

‎doc/src/sgml/catalogs.sgml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,11 +14,13 @@
1414
tables. You can drop and recreate the tables, add columns, insert
1515
and update values, and severely mess up your system that way.
1616
Normally, one should not change the system catalogs by hand, there
17-
arealways SQL commands to do that. (For example, <command>CREATE
17+
arenormally SQL commands to do that. (For example, <command>CREATE
1818
DATABASE</command> inserts a row into the
1919
<structname>pg_database</structname> catalog &mdash; and actually
2020
creates the database on disk.) There are some exceptions for
21-
particularly esoteric operations, such as adding index access methods.
21+
particularly esoteric operations, but many of those have been made
22+
available as SQL commands over time, and so the need for direct manipulation
23+
of the system catalogs is ever decreasing.
2224
</para>
2325

2426
<sect1 id="catalogs-overview">

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp