citus

Commit Graph

Author	SHA1	Message	Date
Philip Dubé	74cb168205	Remove Postgres 10 support	2019-10-11 21:56:56 +00:00
Nils Dijk	9c2c50d875	Hookup function/procedure deparsing to our utility hook (#3041 ) DESCRIPTION: Propagate ALTER FUNCTION statements for distributed functions Using the implemented deparser for function statements to propagate changes to both functions and procedures that are previously distributed.	2019-09-27 22:06:49 +02:00
Hanefi Onaldi	66b9f2e887	Deparsing and qualifiying for FUNCTION/PROCEDURE statements (#3014 ) This PR aims to add all the necessary logic to qualify and deparse all possible `{ALTER\|DROP} .. {FUNCTION\|PROCEDURE}` queries. As Procedures are introduced in PG11, the code contains many PG version checks. I tried my best to make it easy to clean up once we drop PG10 support. Here are some caveats: - I assumed that the parse tree is a valid one. There are some queries that are not allowed, but still are parsed successfully by postgres planner. Such queries will result in errors in execution time. (e.g. `ALTER PROCEDURE p STRICT` -> `STRICT` action is valid for functions but not procedures. Postgres decides to parse them nevertheless.)	2019-09-27 19:02:52 +02:00

Author

SHA1

Message

Date

Philip Dubé

74cb168205

Remove Postgres 10 support

2019-10-11 21:56:56 +00:00

Nils Dijk

9c2c50d875

Hookup function/procedure deparsing to our utility hook (#3041 )

DESCRIPTION: Propagate ALTER FUNCTION statements for distributed functions

Using the implemented deparser for function statements to propagate changes to both functions and procedures that are previously distributed.

2019-09-27 22:06:49 +02:00

Hanefi Onaldi

66b9f2e887

Deparsing and qualifiying for FUNCTION/PROCEDURE statements (#3014 )

This PR aims to add all the necessary logic to qualify and deparse all possible `{ALTER|DROP} .. {FUNCTION|PROCEDURE}` queries.

As Procedures are introduced in PG11, the code contains many PG version checks. I tried my best to make it easy to clean up once we drop PG10 support.


Here are some caveats:
- I assumed that the parse tree is a valid one. There are some queries that are not allowed, but still are parsed successfully by postgres planner. Such queries will result in errors in execution time. (e.g. `ALTER PROCEDURE p STRICT` -> `STRICT` action is valid for functions but not procedures. Postgres decides to parse them nevertheless.)

2019-09-27 19:02:52 +02:00

3 Commits (3e5a92d33b4fda560d107a6d28f0d9fc9f2cda43)