diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2016-07-28 13:26:59 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2016-07-28 13:26:59 -0400 |
| commit | f0795b394991874289658fb51d83dce9a11f026e (patch) | |
| tree | e21cde1ef581b0378c4527e9f6d8d2786b21d454 /src | |
| parent | ce100861687353998d3f1c2b28c61447e8102c58 (diff) | |
| download | postgresql-f0795b394991874289658fb51d83dce9a11f026e.tar.gz postgresql-f0795b394991874289658fb51d83dce9a11f026e.zip | |
Improve documentation about CREATE TABLE ... LIKE.
The docs failed to explain that LIKE INCLUDING INDEXES would not preserve
the names of indexes and associated constraints. Also, it wasn't mentioned
that EXCLUDE constraints would be copied by this option. The latter
oversight seems enough of a documentation bug to justify back-patching.
In passing, do some minor copy-editing in the same area, and add an entry
for LIKE under "Compatibility", since it's not exactly a faithful
implementation of the standard's feature.
Discussion: <20160728151154.AABE64016B@smtp.hushmail.com>
Diffstat (limited to 'src')
| -rw-r--r-- | src/backend/parser/parse_utilcmd.c | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/src/backend/parser/parse_utilcmd.c b/src/backend/parser/parse_utilcmd.c index eb4e4212fc9..0ba59927eed 100644 --- a/src/backend/parser/parse_utilcmd.c +++ b/src/backend/parser/parse_utilcmd.c @@ -1010,7 +1010,9 @@ generateClonedIndexStmt(CreateStmtContext *cxt, Relation source_idx, /* * We don't try to preserve the name of the source index; instead, just - * let DefineIndex() choose a reasonable name. + * let DefineIndex() choose a reasonable name. (If we tried to preserve + * the name, we'd get duplicate-relation-name failures unless the source + * table was in a different schema.) */ index->idxname = NULL; |