Note: The following description applies both to Postgres-XC and PostgreSQL if not described explicitly. You can read PostgreSQL as Postgres-XC except for version number, which is specific to each product.
DROP TABLESPACE removes a tablespace from the system.
A tablespace can only be dropped by its owner or a superuser. The tablespace must be empty of all database objects before it can be dropped. It is possible that objects in other databases might still reside in the tablespace even if no objects in the current database are using the tablespace. Also, if the tablespace is listed in the temp_tablespaces setting of any active session, the DROP might fail due to temporary files residing in the tablespace.
Note: The following description applies both to Postgres-XC and PostgreSQL if not described explicitly. You can read PostgreSQL as Postgres-XC except for version number, which is specific to each product.
Do not throw an error if the tablespace does not exist. A notice is issued in this case.
The name of a tablespace.
Note: The following description applies both to Postgres-XC and PostgreSQL if not described explicitly. You can read PostgreSQL as Postgres-XC except for version number, which is specific to each product.
DROP TABLESPACE cannot be executed inside a transaction block.
Note: XCONLY: The following description applies only to Postgres-XC.
DROP TABLESPACE can be run with EXECUTE DIRECT to control tablespace existence on remote nodes. This works for both remote Coordinators and Datanodes but not on this operation is not authorized on node where application client is connected.