检测到您已登录华为云国际站账号,为了您更好的体验,建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
Method Description Return Value (res Result)RowsAffected() Returns the number of rows affected by the INSERT, DELETE, UPDATE, SELECT, MOVE, FETCH, and COPY operations. int64 and error Parent topic: Go API Reference
DBE_PLDEBUGGER.delete_breakpoint Called by the debug end to delete a breakpoint. DBE_PLDEBUGGER.info_breakpoints Called by the debug end to view all breakpoints. DBE_PLDEBUGGER.backtrace Called by the debug end to check the current call stack.
Examples -- Create a schema. gaussdb=# CREATE SCHEMA tpcds; -- Delete the tpcds.reason_t2 table.
Examples -- Create a schema. gaussdb=# CREATE SCHEMA tpcds; -- Delete the tpcds.reason_t2 table.
Delete MyView. 1 2 gaussdb=# DROP VIEW MyView; DROP VIEW Parent topic: Other Operations
the user. gaussdb=# DROP ROLE lche, jim; -- Delete the user group. gaussdb=# DROP GROUP normal_users; Helpful Links CREATE GROUP, DROP GROUP, and ALTER ROLE Parent topic: SQL Syntax
a complete-refresh materialized view. gaussdb=# DROP MATERIALIZED VIEW bar; -- Delete the my_table table. gaussdb=# DROP TABLE my_table; Helpful Links CREATE INCREMENTAL MATERIALIZED VIEW, CREATE MATERIALIZED VIEW, DROP MATERIALIZED VIEW, REFRESH INCREMENTAL MATERIALIZED VIEW, and
Delete MyView. 1 2 gaussdb=# DROP VIEW MyView; DROP VIEW Parent topic: Other Operations
the complete-refresh materialized view. gaussdb=# DROP MATERIALIZED VIEW bar; -- Delete the my_table table. gaussdb=# DROP TABLE my_table; Helpful Links CREATE INCREMENTAL MATERIALIZED VIEW, CREATE MATERIALIZED VIEW, DROP MATERIALIZED VIEW, REFRESH INCREMENTAL MATERIALIZED VIEW,
1 DROP TABLE Run the following command to delete tablespace fspace: 1 2 openGauss=# DROP TABLESPACE fspace; DROP TABLESPACE Only the tablespace owner or system administrator can delete a tablespace.
the tpcds.reason_t1 table. gaussdb=# DROP TABLE tpcds.reason_t1; -- Delete the table. gaussdb=# DROP TABLE tpcds.reason; -- Delete the schema. gaussdb=# DROP SCHEMA tpcds CASCADE; Helpful Links SELECT Suggestions DATABASE You are advised not to re-index a database in a transaction
You can delete manual backups as needed. For details, see Deleting a Manual Backup. Parent topic: Backup and Restoration
The hint is as follows: insert /*+ multinode */ into t values(3,3),(1,1); There are similar constraints on the DELETE and UPDATE statements. You are advised to add the equivalent filter condition of the distribution key to the WHERE condition in the DELETE and UPDATE statements.
the user mapping. gaussdb=# DROP USER MAPPING FOR bob SERVER my_server; -- Delete the foreign server. gaussdb=# DROP SERVER my_server; -- Delete the role. gaussdb=# DROP ROLE bob; Helpful Links CREATE USER MAPPING and DROP USER MAPPING Parent topic: A
the user mapping. gaussdb=# DROP USER MAPPING FOR bob SERVER my_server; -- Delete the foreign server. gaussdb=# DROP SERVER my_server; -- Delete the role. gaussdb=# DROP ROLE bob; Helpful Links ALTER USER MAPPING and DROP USER MAPPING Parent topic: C
a fast-refresh materialized view. gaussdb=# DROP MATERIALIZED VIEW my_imv; -- Delete the ordinary table my_table. gaussdb=# DROP TABLE my_table; -- Delete the tablespace. gaussdb=# DROP TABLESPACE tbs_data1; Helpful Links ALTER MATERIALIZED VIEW, CREATE MATERIALIZED VIEW, CREATE
the complete-refresh materialized view. gaussdb=# DROP MATERIALIZED VIEW my_mv; -- Delete the ordinary table my_table. gaussdb=# DROP TABLE my_table; -- Delete the tablespace. gaussdb=# DROP TABLESPACE tbs_data1; Helpful Links ALTER MATERIALIZED VIEW, CREATE INCREMENTAL MATERIALIZED
GaussDB supports the access of content in an array by using parentheses, and the extend, count, first, last prior, next, exists, trim, and delete functions.
There are three scenarios: COORDINATOR: Delete the idle or invalid connections from the current CN to a specified CN. NODE: Delete the idle or invalid connections from the current CN to a specified DN.
You can also manually run gs_clean -C to delete inactive session data from the table. Data is automatically inserted into PLAN_TABLE_DATA after EXPLAIN PLAN is executed. Therefore, do not manually insert data into or update data in PLAN_TABLE_DATA.