Properly deparse exprs that might appear in some DDLs #7245
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
e.g.:
CREATE SCHEMA my_schema;
CREATE TYPE my_schema.my_dt AS ENUM ('1','2','3');
CREATE FUNCTION my_schema.my_func()
RETURNS int
LANGUAGE sql
AS $$
SELECT 1;
$$;
CREATE TABLE referencing(a int);
SELECT create_distributed_table('referencing', 'a');
SET search_path TO my_schema, public;
ALTER TABLE referencing ADD check (a > my_func());
Also checked the other places we call deparse_expression() and all except the references in PreprocessAlterPolicyStmt() seem to be fine, so fixed them as well.
DESCRIPTION: Fixes a bug that might cause applying some DDLs on shards incorrectly
TODO: needs tests