Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document that we do not support schema'd type names with typmods #8955

Closed
rmloveland opened this issue Nov 17, 2020 · 1 comment · Fixed by #10568
Closed

Document that we do not support schema'd type names with typmods #8955

rmloveland opened this issue Nov 17, 2020 · 1 comment · Fixed by #10568
Assignees

Comments

@rmloveland
Copy link
Contributor

As noted by @otan in cockroachdb/cockroach#56492:

We currently do not support schema'd type names with typmods, e.g. public.geometry(linestring, 4326) in CREATE TABLE t(g public.geometry(linestring, 4326)). Users seeing this in v20.2 from IMPORT PGDUMP must remove the public. to get this to work (i.e. use geometry(linestring,4326) instead). Note public.geometry works today.

This is because complex_type_name does not take any optional attrs.

We should document the above limitation, and the workaround mentioned.

Not clear whether this only affects users of spatial features, or is just more likely to affect them due to the output of various spatial file tools (?). TBD.

@otan
Copy link
Contributor

otan commented Nov 17, 2020

it's because pg_dumps will output the public schema in this way for geometry/geography types.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants