diff options
| author | Alvaro Herrera | 2019-08-07 16:27:47 +0000 |
|---|---|---|
| committer | Alvaro Herrera | 2019-08-07 16:27:47 +0000 |
| commit | 12afc7145c03c212f26fea3a99e016da6a1c919c (patch) | |
| tree | c6d40c3bd9a4403eeb30ce9328a8bdcbd0495a97 | |
| parent | 4e85642d935eb13341584df7776eb76585d45819 (diff) | |
Add comment on no default partition with hash partitioning
Discussion: https://postgr.es/m/20190806222735.GA9535@alvherre.pgsql
| -rw-r--r-- | src/backend/parser/parse_utilcmd.c | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/src/backend/parser/parse_utilcmd.c b/src/backend/parser/parse_utilcmd.c index a9b2f8bacd8..6e5768c66cf 100644 --- a/src/backend/parser/parse_utilcmd.c +++ b/src/backend/parser/parse_utilcmd.c @@ -3727,6 +3727,12 @@ transformPartitionBound(ParseState *pstate, Relation parent, if (spec->is_default) { + /* + * Hash partitioning does not support a default partition; there's no + * use case for it (since the set of partitions to create is perfectly + * defined), and if users do get into it accidentally, it's hard to + * back out from it afterwards. + */ if (strategy == PARTITION_STRATEGY_HASH) ereport(ERROR, (errcode(ERRCODE_INVALID_TABLE_DEFINITION), |