From d043e64c925a21d42bfd28e6c4ca2e44e4b4d356 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dagfinn=20Ilmari=20Manns=C3=A5ker?= Date: Sun, 24 May 2020 21:48:29 +0100 Subject: [PATCH] Add two more missing command and catalog cross-links The two earlier doc patches both modified this paragraph, so these two changes appear to have been lost while resolving the conflict. --- doc/src/sgml/catalogs.sgml | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml index 508bea3bc6..6f2e0d19dc 100644 --- a/doc/src/sgml/catalogs.sgml +++ b/doc/src/sgml/catalogs.sgml @@ -14,13 +14,14 @@ 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 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, 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. + are normally SQL commands to do that. (For example, inserts a row into the pg_database + catalog — and actually creates the database on disk.) There + are some exceptions for 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. -- 2.27.0