Schemas
Table 1 describes the schemas of GaussDB.
Do not create service data of users in a schema that provides functional interfaces, including but not limited to tables and functions (such as dbe_* and pkg_*).
Schema |
Description |
---|---|
blockchain |
Stores the user history table that is automatically created when a tamper-proof table is created in the ledger database. |
dbe_perf |
Diagnoses performance issues and is also the data source of WDR snapshots. After a database is installed, only the initial user and monitoring administrator have permission to view views and functions in the DBE_PERF scheme by default. |
snapshot |
Manages data related to WDR snapshots. By default, the initial user or monitoring administrator can access the data. |
sqladvsior |
Recommends distribution columns. For details, see Distribution Key Recommendation Functions. |
sys |
Provides the system information view APIs. |
pg_catalog |
Maintains system catalog information, including system catalogs and all built-in data types, functions, and operators. |
pg_toast |
Stores large objects (for internal use). |
public |
Public schema, which is used to store public objects. If search_path is not specified and a schema with the same name exists, new tables (and other objects) are created in the schema by default. If no schema with the same name exists, new tables (and other objects) are automatically placed in this public schema. |
dbe_raw |
Advanced function package dbe_raw, which is used to convert raw data, obtain substrings, and calculate the length. |
dbe_session |
Advanced function package dbe_session, which is used to set the value of a specified attribute and support user query and verification. |
dbe_lob |
Advanced function package dbe_lob, which is used to read, write, and copy large files (CLOB/BLOB). |
dbe_match |
Advanced function package dbe_match, which is used to compare character string similarity. |
dbe_task |
Advanced function package dbe_task, which is used to schedule job tasks, including submitting tasks, canceling tasks, synchronizing task status, and updating task information, so that the database can periodically execute specific tasks. |
dbe_sql |
Advanced function package dbe_sql, which is used to execute dynamic SQL statements and construct query and other commands during application running. |
dbe_file |
Advanced function package dbe_file, which is used to read, copy, write, delete, and rename external database files. |
dbe_output |
Advanced function package dbe_output, which is used to print output information. |
dbe_random |
Advanced function package dbe_random, which is used to generate random seeds and random numbers. |
dbe_application_info |
Advanced function package dbe_application_info, which is used for recording client information. |
dbe_utility |
Advanced function package dbe_utility, which is used to invoke the debugging tool in a stored procedure, for example, to print error stacks. |
dbe_scheduler |
Advanced function package dbe_scheduler, which is used to create scheduled tasks and enable the database to periodically execute specified tasks through programs and schedules. You can also perform external database tasks by authorizing and providing certificates. |
information_schema |
Stores information about objects defined in the current database. |
dbe_sql_util |
SQL O&M function, including the O&M interface of SQL patches. |
dbe_xmlgen |
Advanced function package dbe_xmlgen, which is used to convert query results into XML character strings. |
dbe_describe |
Advanced function package dbe_describe, which is used to query parameter information about stored procedures or functions. |
Schema |
Description |
---|---|
dbe_pldebugger |
This view is used to debug PL/SQL functions and stored procedures. Currently, this view is not supported. An error message "unsupported" is displayed when the interface is invoked in this view. |
db4ai |
Manages data of different versions in AI training. |
dbe_pldeveloper |
Compiles and debugs user stored procedures. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot