CN114610351A - Database upgrading method - Google Patents
Database upgrading method Download PDFInfo
- Publication number
- CN114610351A CN114610351A CN202210242510.4A CN202210242510A CN114610351A CN 114610351 A CN114610351 A CN 114610351A CN 202210242510 A CN202210242510 A CN 202210242510A CN 114610351 A CN114610351 A CN 114610351A
- Authority
- CN
- China
- Prior art keywords
- database
- upgrading
- script
- node
- upgrade
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1433—Saving, restoring, recovering or retrying at system level during software upgrading
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1469—Backup restoration techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Quality & Reliability (AREA)
- Computer Security & Cryptography (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a database upgrading method, which comprises the following steps: the upgrade package is put into the data node to be upgraded to realize the preparation for upgrading; according to the upgrade preparation, upgrading the database; and verifying whether the database is successfully upgraded or not, and determining whether to submit the upgrade or not according to a verification result. Wherein, according to the preparation for upgrading, carry out upgrading to the database, include: searching a main node capable of executing the upgrading SQL script; backing up a system table and a configuration file on each node; screening and collecting scripts to be executed, and setting a main node into an upgrading mode; and updating the database according to the screened and collected scripts to complete the execution of the upgrade. The database upgrading method has the advantages of smaller related range, simple steps, less occupied resources and more complete execution result, and can effectively save development and operation and maintenance costs.
Description
Technical Field
The invention relates to the technical field of database upgrading, in particular to a database upgrading method.
Background
Database upgrades are a common problem in database usage. With the update of the database version, a user needs to upgrade the old version database to the new version database in order to obtain a new function of the new version database, and when the database is updated, the old version database needs to be migrated to the new version database in order to protect the safety of user data and ensure the continuous and smooth operation of user services.
The traditional database upgrading is a process of importing and exporting data, namely exporting data of an old database into an SQL script (or in other forms), then establishing a new version database, and finally importing the data of the old database version into the new version database to complete the upgrading of the version, wherein the importing process is a process of executing an SQL script to rebuild the data of the old database. In practical applications, the upgrade mechanism has the following disadvantages: 1) the upgrading process relates to all data of the database, the workload is large, and the upgrading process occupies more resources; 2) the upgrading step is complicated, and development is needed or an administrator is very familiar with the upgrading process; 3) some database information data, such as OID (object identifier) etc., will be altered after export and import.
Therefore, how to provide a database upgrading method, which reduces development and operation maintenance costs while simplifying the upgrading process, is a technical problem to be solved urgently.
Disclosure of Invention
In view of this, the present invention provides a database upgrading method to solve the deficiencies of the conventional database upgrading.
In one aspect, the present invention provides a database upgrading method, including:
step S1: the upgrade package is put into the data node to be upgraded to realize the preparation for upgrading;
step S2: according to the upgrade preparation, upgrading the database;
step S3: and verifying whether the database is successfully upgraded or not, and determining whether to submit the upgrade or not according to a verification result.
Further, the database upgrading method of the present invention further includes: after the database is upgraded successfully, all information of the database can be restored to the old database state through manual rollback.
Further, in step S2, according to the preparation for upgrading, the upgrading is performed on the database, including:
step S201: searching a main node capable of executing the upgrading SQL script;
step S202: backing up a system table and a configuration file on each node;
step S203: screening and collecting scripts to be executed, and setting a main node into an upgrading mode;
step S204: and updating the database according to the screened and collected scripts to finish the execution of upgrading.
Further, in step S201, when the database is deployed as a single node, the single node itself is used as a master node; when the database is deployed as highly available, the master library is taken as the master node.
Further, in step S202, backing up the system table and the configuration file on each node includes: traversing all databases on each node, and backing up the system tables stored in the databases; the configuration files that depend on the respective nodes are backed up.
Further, in step S203, the screening and collecting the scripts that need to be executed includes:
the method comprises the steps that the kernel version number is used for carrying out upgrading management on a database kernel, when the updating of a function involves the change of a system table structure and content, a corresponding script is compiled for the function, the script comprises an upgrading script and a rollback script, the name of the script comprises the kernel version number, and the script to be executed is screened out according to the kernel version numbers of a new database and an old database;
collecting the contents of the upgrading script into an SQL file from small to large according to the increasing relation of the kernel version number; and collecting the contents of the rollback script into an SQL file from large to small according to the increasing relation of the kernel version number, and respectively wrapping the SQL file by adopting transaction blocks so as to ensure the atomicity of execution.
Further, in step S204, updating the database according to the screened and aggregated scripts, and completing the execution of the upgrade, including:
sequentially executing a preposed rollback script and a preposed upgrading script on a database; the pre-roll script and the pre-upgrade script respectively comprise a maildb script and an otherdb script, wherein the maildb script is only executed in a postgres database, and the otherdb script is executed in all databases except the postgres database;
managing the binary file through the soft connection, pointing the soft connection to the binary file of the new database, updating the binary file of the database, and restarting a database management system;
sequentially executing a post-rollback script and a post-upgrading script on the database; the post-roll script and post-upgrade script each contain a mailb script that executes only in the postgres database and an otherdb script that executes in all but the postgres database.
Further, in step S2, according to the preparation for upgrading, the method further includes, when the upgrading cannot be performed any more due to an error in the process of performing upgrading on the database, gradually rolling back to a state before upgrading according to the upgrading process and the backup information, and specifically includes:
when the rollback script is successfully executed, the recovery of the system table is only executed in the main library;
when the rollback script fails to be executed, the system table is restored in a covering mode on each node by using the physical file backed up on each node; the rollback dependent on the configuration information of the respective node is restored in an overlay manner at each node using the physical files backed up on each node.
In another aspect, the present invention also provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the method.
Finally, the invention also provides a computer device comprising a memory, a processor and a computer program stored on said memory and executable on said processor, said processor implementing the steps of said method when executing said program.
Compared with the traditional upgrading mode, the database upgrading method has the advantages of smaller related range, simple steps, less occupied resources and more complete execution result, and can effectively save development and operation and maintenance costs.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a flowchart of a method of upgrading a database according to an exemplary first embodiment of the present invention.
Fig. 2 is an execution flowchart of a database upgrading method according to an exemplary first embodiment of the present invention.
Fig. 3 is a flowchart of a method for performing an upgrade in a database upgrade method according to an exemplary second embodiment of the present invention.
Fig. 4 is a flowchart illustrating an upgrade execution in a database upgrade method according to an exemplary second embodiment of the present invention.
Detailed Description
Embodiments of the present invention will be described in detail below with reference to the accompanying drawings.
It should be noted that, in the case of no conflict, the features in the following embodiments and examples may be combined with each other; moreover, all other embodiments that can be derived by one of ordinary skill in the art from the embodiments disclosed herein without making any creative effort fall within the scope of the present disclosure.
It is noted that various aspects of the embodiments are described below within the scope of the appended claims. It should be apparent that the aspects described herein may be embodied in a wide variety of forms and that any specific structure and/or function described herein is merely illustrative. Based on the disclosure, one skilled in the art should appreciate that one aspect described herein may be implemented independently of any other aspects and that two or more of these aspects may be combined in various ways. For example, an apparatus may be implemented and/or a method practiced using any number of the aspects set forth herein. Additionally, such an apparatus may be implemented and/or such a method may be practiced using other structure and/or functionality in addition to one or more of the aspects set forth herein.
The theoretical technology of the invention is briefly described as follows:
the method for upgrading the database can be divided into two categories, wherein the first category is the database upgrading which can achieve the purpose of upgrading by directly replacing the binary file of the database; the second type is database upgrading which can achieve the purpose of upgrading by modifying database data on the basis of the first type. The reason for modifying the database data is that when the structure and content of the system table in the new database are changed, the data of the old database and the data structure and content of the new database are incompatible, so that the update cannot be completed by directly replacing the binary file of the database. From the perspective of optimizing the upgrading process, how to upgrade the database needing to modify data in an in-situ upgrading mode is an important way for simplifying upgrading and reducing development and operation maintenance costs.
OpenGauss may provide a way to modify system tables by supporting an upgrade mode switch upgrade _ mode. In the mode, not only the structure and the content of the system table can be changed through the SQL statement, but also the used OID can be specified for the object newly built through the SQL statement. Therefore, for the new function introduced in the new version of database, the purpose of upgrading can be achieved through the replacement of the binary file and the execution of the SQL script on the basis of the old version of database.
The terms to which the invention relates are to be interpreted as follows:
in-place upgrading: compared with the traditional method for upgrading the database by importing and exporting, the method has the advantages that the data is not required to be imported and exported in the original site upgrading, and the upgrading operation is directly carried out on the original data.
OpenGauss: an open source relational database with a kernel derived from PostgreSQL is issued by adopting a Loran loose license agreement, has the characteristics of high performance, high availability, high safety, easy operation and maintenance and full opening, and is oriented to a transaction application with large concurrency and large data volume and mainly based on-line transaction processing, an Internet of things data application scene with more sensing monitoring equipment, high sampling rate, data storage as an additional model and heavy operation and analysis.
SQL: structured Query Language (SQL), a high-level non-procedural database Query and programming Language, has data definition, data manipulation, and data control functions for accessing data and querying, updating, and managing relational database systems.
OID: an Object Identifier (OID), or simply OID, is a globally unique value associated with an Object to unambiguously identify the Object, which ensures that the Object is correctly located and managed in communications and information processing. In general, OID is the identity card of the object in network communication.
Kernel version number: the form is { kernel large version number } { kernel small version number }, which is used for indicating the change on the structure and the content of the system table and is monotonically increased.
Script: involving an upgrade script and a rollback script, which are described below,
TABLE 1
It should be noted that the pre-script is a script that needs to be executed before being upgraded to the binary system of the new database, and the post-script is a script that needs to be executed after being upgraded to the binary system of the new database. The name of the script comprises a prefix and a suffix, the prefix of the name of the script is shown in table 1, and the format of the suffix of the name of the script is as follows: { kernel major version number } _{ kernel minor version number }. sql. When the updated system table is shared among databases, only the updated SOL/rollback SQL is written in a mailb type script (mailb in OpenGauss is a postgres database, and all the rest databases are called other dbs); when the upgraded system table is not shared between databases, the upgrade SQL/rollback SQL is written in the maildb and the other db.
Main library and standby library: when the high-availability database is used, only one standby database can be provided, the main database is used for customer service, and the standby database is used for data backup of the main database; when high availability is not used (single node), only the master library has no spare library at this time.
Fig. 1 is a flowchart of a method of upgrading a database according to an exemplary first embodiment of the present invention. As shown in fig. 1, the database upgrading method in this embodiment includes:
step S1: the upgrade package is put into the data node to be upgraded to realize the preparation for upgrading;
step S2: according to the upgrade preparation, upgrading the database;
step S3: and verifying whether the database is successfully upgraded or not, and determining whether to submit the upgrade or not according to a verification result.
Fig. 2 is a flowchart illustrating an implementation of a database upgrading method according to an exemplary first embodiment of the present invention, and fig. 2 is a preferred implementation of the database upgrading method shown in fig. 1. As can be seen from fig. 2, the database upgrade method in the present exemplary embodiment submits an upgrade when the database upgrade is successful, and at this time, automatic rollback is not supported; rolling back the version when the database is not upgraded successfully; after the database is upgraded successfully, all information of the database can be restored to the old database state through manual rollback.
Fig. 3 is a flowchart of a method of upgrading a database according to an exemplary second embodiment of the present invention. Fig. 3 is a preferred embodiment of the database upgrading method shown in fig. 1. As shown in fig. 3, the database upgrading method according to the embodiment performs upgrading on a database, including:
step S201: searching a main node capable of executing the SQL upgrading script;
step S202: backing up a system table and a configuration file on each node;
step S203: screening and collecting scripts to be executed, and setting a main node into an upgrading mode;
step S204: updating the database according to the screened and collected scripts to complete the execution of upgrading;
specifically, in step S201, when the database is deployed as a single node, the single node itself is used as a master node; when a database deployment is highly available (i.e., there is a master/standby/cascaded standby), the master is taken as the master node.
In step S202, the step of backing up the system table and the configuration file on each node includes: traversing all databases on each node, and backing up the system tables stored in the databases; the configuration files dependent on the respective nodes are backed up.
In step S203, the screening and collecting the scripts to be executed includes:
in order to facilitate management of upgrading, a kernel version number is used for managing upgrading of a database kernel, when updating of a function involves changing of a system table structure and content, a corresponding script is compiled for the function, the script comprises an upgrading script and a rollback script, the name of the script comprises the kernel version number, and the script to be executed is screened out according to the kernel version numbers of a new database and an old database during upgrading;
collecting the contents of the upgrading script into an SQL file from small to large according to the increasing relation of the kernel version number; and collecting the contents of the rollback script into an SQL file from large to small according to the increasing relation of the kernel version number, and respectively wrapping the SQL file by adopting transaction blocks so as to ensure the atomicity of execution.
In step S204, updating the database according to the screened and collected scripts to complete the execution of the upgrade, including:
sequentially executing a preposed rollback script and a preposed upgrading script on a database; the pre-roll script and the pre-upgrade script respectively comprise a maildb script and an otherdb script, wherein the maildb script is only executed in a postgres database, and the otherdb script is executed in all databases except the postgres database;
managing the binary file through the soft connection, pointing the soft connection to the binary file of the new database, updating the binary file of the database, and restarting a database management system;
sequentially executing a post-rollback script and a post-upgrading script on the database; the post-roll script and post-upgrade script each contain a mailb script that executes only in the postgres database and an otherdb script that executes in all but the postgres database.
In step S2, according to the upgrade preparation, the upgrade is performed on the database, and when the upgrade cannot be performed any more due to an error occurring in the process of performing the upgrade on the database, the method may gradually rollback to the state before the upgrade according to the upgrade process and the backup information, specifically, the method includes:
when the rollback script is successfully executed, the recovery of the system table is only executed in the main library;
when the rollback script fails to be executed, the system table is restored in a covering mode on each node by using the physical file backed up on each node; the rollback dependent on the configuration information of the respective node is restored in an overlay manner at each node using the physical files backed up on each node. The rollback is realized mainly by in-place backup of database data, the backup contents include system tables, configuration information and the like, the configuration information includes postgresql.conf, pg _ hba.conf and the like, and all the contents are not required to be backed up.
Fig. 4 is an execution flowchart of a database upgrading method according to an exemplary second embodiment of the present invention, and a method for executing upgrading in the database upgrading method shown in fig. 3 is specifically executed according to the flowchart shown in fig. 4.
The invention also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, carries out the steps of the method.
The invention also provides a computer device comprising a memory, a processor and a computer program stored on said memory and executable on said processor, said processor implementing the steps of said method when executing said program.
The medium and the computer device have the corresponding technical effects of the database upgrading method.
The above description is only for the specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. A database upgrade method, the method comprising:
step S1: the upgrade package is put into the data node to be upgraded to realize the preparation for upgrading;
step S2: according to the upgrade preparation, upgrading the database;
step S3: and verifying whether the database is successfully upgraded or not, and determining whether to submit the upgrade or not according to a verification result.
2. The database upgrading method according to claim 1, further comprising: after the database is upgraded successfully, all information of the database can be restored to the old database state through manual rollback.
3. The database upgrading method according to claim 1, wherein in step S2, according to the upgrade preparation, the upgrading is performed on the database, including:
step S201: searching a main node capable of executing the upgrading SQL script;
step S202: backing up a system table and a configuration file on each node;
step S203: screening and collecting scripts to be executed, and setting a main node into an upgrading mode;
step S204: and updating the database according to the screened and collected scripts to finish the execution of upgrading.
4. The database upgrading method according to claim 3, wherein in step S201, when the database is deployed as a single node, the single node itself is used as a master node; when the database is deployed as highly available, the master library is taken as the master node.
5. The database upgrading method according to claim 4, wherein in step S202, backing up the system table and configuration file on each node comprises: traversing all databases on each node, and backing up the system tables stored in the databases; the configuration files dependent on the respective nodes are backed up.
6. The database upgrading method according to claim 5, wherein in step S203, the screening and assembling the scripts to be executed comprises:
the method comprises the steps that the kernel version number is used for carrying out upgrading management on a database kernel, when the updating of a function involves the change of a system table structure and content, a corresponding script is compiled for the function, the script comprises an upgrading script and a rollback script, the name of the script comprises the kernel version number, and the script to be executed is screened out according to the kernel version numbers of a new database and an old database;
collecting the contents of the upgrading script into an SQL file from small to large according to the increasing relation of the kernel version number; and collecting the contents of the rollback script into an SQL file from large to small according to the increasing relation of the kernel version number, and respectively wrapping the SQL file by adopting transaction blocks so as to ensure the atomicity of execution.
7. The database upgrading method according to claim 6, wherein in step S204, updating the database according to the filtered and aggregated scripts to complete the upgrading, comprises:
sequentially executing a preposed rollback script and a preposed upgrading script on a database; the pre-roll script and the pre-upgrade script respectively comprise a maildb script and an otherdb script, wherein the maildb script is only executed in a postgres database, and the otherdb script is executed in all databases except the postgres database;
managing the binary file through the soft connection, pointing the soft connection to the binary file of the new database, updating the binary file of the database, and restarting a database management system;
sequentially executing a post-rollback script and a post-upgrading script on the database; the post-roll script and post-upgrade script each contain a mailb script that executes only in the postgres database and an otherdb script that executes in all but the postgres database.
8. The database upgrading method according to claim 3, wherein in step S2, the database is upgraded according to the preparation for upgrading, and further comprising, when the upgrading process of the database cannot be performed any more due to an error, implementing automatic rollback to the pre-upgrading state according to the upgrading process and the backup information, specifically, the method includes:
when the rollback script is successfully executed, the recovery of the system table is only executed in the main library;
when the rollback script fails to be executed, the system table is restored in a covering mode on each node by using the physical file backed up on each node; the rollback dependent on the configuration information of the respective node is restored in an overlay manner at each node using the physical files backed up on each node.
9. A computer-readable storage medium, having stored thereon a computer program, which when executed by a processor, carries out the steps of the method of any one of claims 1-8.
10. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the method as claimed in any one of claims 1 to 8 when the program is executed by the processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210242510.4A CN114610351A (en) | 2022-03-11 | 2022-03-11 | Database upgrading method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210242510.4A CN114610351A (en) | 2022-03-11 | 2022-03-11 | Database upgrading method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114610351A true CN114610351A (en) | 2022-06-10 |
Family
ID=81863867
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210242510.4A Pending CN114610351A (en) | 2022-03-11 | 2022-03-11 | Database upgrading method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114610351A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116011026A (en) * | 2023-03-23 | 2023-04-25 | 西安热工研究院有限公司 | Database configuration security rapid verification method, system, equipment and storage medium |
-
2022
- 2022-03-11 CN CN202210242510.4A patent/CN114610351A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116011026A (en) * | 2023-03-23 | 2023-04-25 | 西安热工研究院有限公司 | Database configuration security rapid verification method, system, equipment and storage medium |
| CN116011026B (en) * | 2023-03-23 | 2023-06-16 | 西安热工研究院有限公司 | Database configuration security rapid verification method, system, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111061817B (en) | Adaptive business construction system, method and computer readable medium | |
| US20230394029A1 (en) | Update and query of a large collection of files that represent a single dataset stored on a blob store | |
| KR102141234B1 (en) | Versioned hierarchical data structure within a distributed data store | |
| US9280554B2 (en) | Using confidence values for synchronizing file systems | |
| US9558207B1 (en) | Versioning of database partition maps | |
| CN112463450B (en) | Incremental backup management method, system, electronic equipment and storage medium | |
| US20050120344A1 (en) | Optimal component installation | |
| CN111881223A (en) | Data management method, device, system and storage medium | |
| US11704335B2 (en) | Data synchronization in a data analysis system | |
| CN111752901A (en) | Index creation method and device, electronic equipment and storage medium | |
| CN112434008A (en) | Distributed database upgrading method, device and medium | |
| CN114610351A (en) | Database upgrading method | |
| CN114942965A (en) | Method and system for accelerating synchronous operation of main database and standby database | |
| US11797523B2 (en) | Schema and data modification concurrency in query processing pushdown | |
| CN109271199A (en) | A kind of method and system for database continuous integrating and script file management | |
| CN112835887A (en) | Database management method, database management device, computing equipment and storage medium | |
| CN114138560A (en) | Backup restoration method and system for operating system | |
| CN112463447A (en) | Optimization method for realizing physical backup based on distributed database | |
| CN114328546A (en) | Timestamp mode determination method and device of database management system | |
| CN112749156A (en) | Data processing method, database management system and data processing equipment | |
| US11874796B1 (en) | Efficient garbage collection in optimistic multi-writer database systems | |
| CN113220638B (en) | Method and system for establishing database snapshot by using container technology | |
| US20230418711A1 (en) | Repairing unresolved dangling references after failover | |
| CN116150126A (en) | Data processing method, device, electronic equipment and storage medium | |
| CN118519987A (en) | Database management system upgrading and downgrading method, device, equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |