diff options
| author | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2014-01-27 09:32:51 +0200 |
|---|---|---|
| committer | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2014-01-27 09:33:18 +0200 |
| commit | f62eba204f367acbfea7e63991524bf981b307f8 (patch) | |
| tree | c82b314aabd10a61661e718f99a2fdd551feb091 | |
| parent | 2850896961994aa0993b9e2ed79a209750181b8a (diff) | |
| download | postgresql-f62eba204f367acbfea7e63991524bf981b307f8.tar.gz postgresql-f62eba204f367acbfea7e63991524bf981b307f8.zip | |
Fix typo in README
Amit Langote
| -rw-r--r-- | src/backend/catalog/README | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/catalog/README b/src/backend/catalog/README index fce01ea4314..7e0ddf312dd 100644 --- a/src/backend/catalog/README +++ b/src/backend/catalog/README @@ -92,7 +92,7 @@ them. Thus, the variable-length fields must all be at the end, and only the variable-length fields of a catalog tuple are permitted to be NULL. For example, if you set pg_type.typrelid to be NULL, a piece of code will likely perform "typetup->typrelid" (or, worse, -"typetyp->typelem", which follows typrelid). This will result in +"typetup->typelem", which follows typrelid). This will result in random errors or even segmentation violations. Hence, do NOT insert catalog tuples that contain NULL attributes except in their variable-length portions! (The bootstrapping code is fairly good about |