diff options
| author | Robert Haas <rhaas@postgresql.org> | 2012-05-22 11:19:33 -0400 |
|---|---|---|
| committer | Robert Haas <rhaas@postgresql.org> | 2012-05-22 11:23:36 -0400 |
| commit | 8fbe5a317de6c91826ae2c91f73f780bb0d6489e (patch) | |
| tree | fd48724df7f192a058d86dc00a23cf92cf33c05f /contrib | |
| parent | b536458e73a8d9294817228f06961913f6faa551 (diff) | |
Fix error message for COMMENT/SECURITY LABEL ON COLUMN xxx IS 'yyy'
When the column name is an unqualified name, rather than table.column,
the error message complains about too many dotted names, which is
wrong. Report by Peter Eisentraut based on examination of the
sepgsql regression test output, but the problem also affects COMMENT.
New wording as suggested by Tom Lane.
Diffstat (limited to 'contrib')
| -rw-r--r-- | contrib/sepgsql/expected/label.out | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contrib/sepgsql/expected/label.out b/contrib/sepgsql/expected/label.out index f9587dee57a..d4a6f8ae962 100644 --- a/contrib/sepgsql/expected/label.out +++ b/contrib/sepgsql/expected/label.out @@ -91,7 +91,7 @@ SECURITY LABEL ON TABLE t2 ERROR: SELinux: invalid security label: "invalid security context" SECURITY LABEL ON COLUMN t2 IS 'system_u:object_r:sepgsql_ro_table_t:s0'; -- be failed -ERROR: improper relation name (too many dotted names): +ERROR: column name must be qualified SECURITY LABEL ON COLUMN t2.b IS 'system_u:object_r:sepgsql_ro_table_t:s0'; -- ok -- |