A method, device, equipment and storage medium for deleting database partition online

Abstract

The application provides a method and device for deleting a database partition online, an equipment and a storage medium, and applies to the technical field of databases. The method comprises the following steps: according to a partition deletion instruction, executing a first transaction on a target partition in a normal use state corresponding to the partition deletion instruction, wherein the first transaction comprises modifying a partition state corresponding to the target partition from the normal use state to a deleting state, and the deleting state is used for indicating that no new DDL operation and DML operation is executed; after detecting that the first transaction is submitted, executing a second transaction on the target partition, wherein the second transaction comprises executing a metadata deletion operation if it is detected that all other transactions accessing the target partition are ended, and modifying the partition state corresponding to the target partition from the deleting state to a deleted state after the metadata deletion operation is successful. The application reduces the difficulty of transaction execution, avoids the blocking of high-frequency concurrent DML operations, and further improves the concurrent performance of DML operations during the deletion of the partition.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of database, in particular to a method and device for online deleting database partition, equipment and storage medium. BACKGROUND

[0002] The database supports data definition language (Data Definition Language, DDL) operations such as adding partitions to a partitioned table and deleting partitions; and also supports data manipulation language (Data Manipulation Language, DML) operations such as querying, adding, updating and deleting a partitioned table.

[0003] During the operation of deleting a partition from a partitioned table, there may be DML operations such as querying, adding, updating and deleting the partitioned table at the same time; data snapshots are used to ensure data consistency during DML operations. In order to ensure data consistency, the database adds a blocking partition object lock to the partitioned table at the commit stage when deleting a partition, which blocks the DML operations on the partitioned table. In addition, an 8-level lock is added to the partition to be deleted to avoid other concurrent transactions accessing the data in the partition during the deletion of the partition.

[0004] The operation of deleting a partition involves updating the metadata of the partitioned table, which is more complex than the DML operations on the partitioned table, and the frequency of deleting a partition is relatively low compared to the DML operations, which can cause blocking of high-frequency concurrent DML operations and reduce the concurrent performance of DML operations when deleting a partition. SUMMARY

[0005] At least one embodiment of the present application provides a method, device, equipment and storage medium for online deleting a database partition, which solves the problem that the operation of deleting a partition in the prior art causes blocking of high-frequency concurrent DML operations and reduces the concurrent performance of DML operations when deleting a partition.

[0006] To solve the above technical problems, the present application is implemented as follows:

[0007] In a first aspect, the embodiments of the present application provide a method for online deleting a database partition, comprising:

[0008] According to the partition deletion instruction, a first transaction is executed on a target partition in a normal use state corresponding to the partition deletion instruction, the first transaction comprising modifying the partition state corresponding to the target partition from the normal use state to a deleting state, the deleting state being used to indicate that no new DDL operation and DML operation is executed;

[0009] After detecting that the first transaction is committed, a second transaction is executed on the target partition, the second transaction comprising: if it is detected that all other transactions currently accessing the target partition are ended, a metadata deletion operation is executed, and after the metadata deletion operation is successful, a partition state corresponding to the target partition is modified from the deleting state to a deleted state.

[0010] Preferably, the method as described above further comprises:

[0011] When the first transaction is executed, a partition state protection lock for isolating concurrent structure changes is further set for a partition table corresponding to the target partition;

[0012] When the second transaction is executed, the partition state protection lock is further released after the metadata deletion operation is successful.

[0013] Preferably, the method as described above further comprises:

[0014] If it is detected that the metadata deletion operation of the target partition fails, the second transaction is executed again on the target partition according to a preset clear partition syntax.

[0015] Specifically, the method as described above, the second transaction is executed again on the target partition according to a preset clear partition syntax further comprises:

[0016] Before the metadata deletion operation is executed, an exclusive deletion lock for guaranteeing atomicity of metadata operation is set for a partition table corresponding to the target partition;

[0017] After the metadata deletion operation is executed, all locks corresponding to the partition table are released.

[0018] Preferably, the method as described above further comprises:

[0019] When a DDL operation is executed on a partition table corresponding to the target partition, if it is detected that the target partition is in the deleting state, preset error information corresponding is fed back.

[0020] Preferably, the method as described above further comprises:

[0021] When an obtaining valid partition list operation in a DML operation is executed on a partition table corresponding to the target partition, if it is detected that the target partition is in the deleting state, the target partition is skipped.

[0022] In a second aspect, an embodiment of the present application provides a control device, comprising:

[0023] The first processing module is configured to execute a first transaction on a target partition in a normal use state corresponding to the partition deletion instruction according to the partition deletion instruction, and the first transaction comprises modifying a partition state corresponding to the target partition from the normal use state to a deleting state, and the deleting state is used to indicate that no new data definition language (DDL) operation and data manipulation language (DML) operation is executed.

[0024] The second processing module is configured to execute a second transaction on the target partition after the first transaction is submitted, and the second transaction comprises executing a metadata deletion operation if it is detected that all other transactions currently accessing the target partition are ended, and modifying the partition state corresponding to the target partition from the deleting state to a deleted state after the metadata deletion operation is successful.

[0025] In a third aspect, an electronic device is provided, which includes a processor, a memory, and a program stored in the memory and capable of running on the processor. When the program is executed by the processor, the steps of the method for online deleting a database partition are implemented.

[0026] In a fourth aspect, a computer readable storage medium is provided, which stores a computer program. When the computer program is executed by a processor, the steps of the method for online deleting a database partition are implemented.

[0027] In a fifth aspect, a computer program product is provided, which includes computer instructions. When the computer instructions are executed by a processor, the steps of the method for online deleting a database partition are implemented.

[0028] Compared with the prior art, the method, device, equipment and storage medium for online deleting a database partition provided by the embodiments of the present application can reduce the difficulty of transaction execution when a target partition is deleted by dividing a deletion partition operation with a low frequency into two independent transactions, dividing a partition state into a normal use state, a deleting state and a deleted state, avoiding the occurrence of a DDL operation on the partition table again during the deletion of the partition, and ensuring the consistency of data, avoiding the blocking of high-frequency concurrent DML operations, and improving the concurrent performance of DML operations during the deletion of the partition. BRIEF DESCRIPTION OF DRAWINGS

[0029] Various other advantages and benefits will become apparent to those of ordinary skill in the art, upon reading the following detailed description of the preferred embodiment. The accompanying drawings are included to provide a description of preferred embodiments, and are not meant to limit the present application. Furthermore, the same reference numerals in different drawings represent the same elements. In the drawings:

[0030] Figure 1 A flowchart of one of the methods for online deleting database partition in the embodiments of the present application;

[0031] Figure 2 A flowchart of another of the methods for online deleting database partition in the embodiments of the present application;

[0032] Figure 3 A flowchart of another of the methods for online deleting database partition in the embodiments of the present application;

[0033] Figure 4 A structure diagram of the control device in the embodiments of the present application. DETAILED DESCRIPTION

[0034] Exemplary embodiments of the present application will be described herein below with reference to the accompanying drawings. While exemplary embodiments of the present application are illustrated, it is to be understood that the present application is not limited to the embodiments described herein, but can be practiced with variation within the spirit and scope of the present application, as disclosed by the appended claims.

[0035] The terms "first", "second", and the like, as used in the description and the claims of this application, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the use of the terms so construed can interchange depending upon the context in which it is used. Furthermore, the terms "comprise", "have" and any variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements is not necessarily limited to those elements, but can include other elements not expressly listed or inherent to such process, method, article, or apparatus. The term "and / or" includes at least one of the referenced items, such as A and / or B, which is to be interpreted as meaning that A is present or B is present or both A and B are present.

[0036] Referring now to the Figure 1 The method for online deleting database partition provided by the embodiments of the present application comprises the following steps:

[0037] Step S101, according to the partition deletion instruction, a first transaction is executed on a target partition corresponding to the partition deletion instruction and in a normal use state, the first transaction includes modifying the partition state corresponding to the target partition from the normal use state to a deleting state, the deleting state is used to indicate that no new DDL operation and DML operation is executed;

[0038] Step S102, after detecting that the first transaction is committed, a second transaction is executed on the target partition, the second transaction includes if it is detected that all other transactions currently accessing the target partition are ended, a metadata deletion operation is executed, and after the metadata deletion operation is successful, the partition state corresponding to the target partition is modified from the deleting state to a deleted state.

[0039] In the embodiment, in order to realize online deletion of the database partition, the partition deletion operation is divided into two independent transactions, i.e., the first transaction and the second transaction, and the partition state is divided into three states, i.e., the normal use state, the deleting state and the deleted state. By dividing the deletion partition operation into two independent transactions, the transaction mechanism in the database can be effectively utilized, and the difficulty of creating and / or ending a transaction is reduced. When the partition state is in the normal use state, all DDL operations and DML operations can be executed. When the partition state is in the deleting state, only the accessed DDL operation and DML operation are executed, and no new DDL operation and DML operation is executed. When the partition state is in the deleted state, no new DDL operation and DML operation is executed.

[0040] Based on the above division of the transaction and the partition state, after the database receives a partition deletion instruction for indicating deletion of a partition, a first transaction is executed on a target partition corresponding to the partition deletion instruction and in a normal use state, and a second transaction is executed after the first transaction is committed. Specifically, the first transaction includes modifying the partition state of the target partition from the normal use state to the deleting state in which no new DDL operation and DML operation is executed. Thus, before the transaction is committed, other DML operations can normally access the partition. Concurrent DML operations started after the transaction is committed will detect that the partition state is in the deleting state, so that the partition is skipped when an effective partition list is obtained.

[0041] The second transaction includes performing a metadata deletion operation after detecting that all other transactions currently accessing the target partition are ended, and modifying the partition state to the deleted state after the metadata deletion operation is successful. The second transaction avoids affecting the deletion of the partition by executing new DDL operations and DML operations, does not block the DDL operation and / or other concurrent DML operation which has been started, and ensures smooth execution of the accessed operation, thereby facilitating improvement of the concurrent performance of the DML operation during deletion of the partition.

[0042] In summary, the application divides the deletion partition operation with low frequency into two independent transactions, and divides the partition state into normal use state, deleting state and deleted state, so that when the target partition is deleted, the transaction execution difficulty can be reduced, and the DDL operation on the partition table is avoided during the deletion partition process, and the concurrent DML can be processed according to the state of the deletion partition, ensuring the consistency of the data, avoiding the blocking of high-frequency concurrent DML operation, and improving the concurrent performance of DML operation during deletion partition.

[0043] Specifically, to implement the above method, the insertion operation module of the database can be expanded. When the insertion operation module detects that the partition state is in the deleting state during the insertion of data, it is skipped. If the partition state is in the normal use state, the insertion operation module allows data to be inserted into the partition.

[0044] Here, the insertion operation module is a module for performing DML operations such as adding, deleting, updating, etc. The expanded insertion operation module can ensure that DML operations are not concurrent when the partition state is in the deleting state. When the partition state is in the normal use state, the insertion operation module allows DML operations such as adding, deleting, updating, etc. to be performed on the partition.

[0045] Preferably, the method described above further comprises:

[0046] When the first transaction is executed, a partition state protection lock for isolating concurrent structural changes is also set for the partition table corresponding to the target partition;

[0047] When the second transaction is executed, the partition state protection lock is released after the metadata deletion operation is successful.

[0048] In this embodiment, on the basis of the above-mentioned deletion partition, a partition state protection lock for isolating concurrent structural changes is also set for the partition table in the first transaction, and the partition state protection lock is released after the metadata deletion operation is successful in the second transaction. Through the setting of the partition state protection lock, it is further ensured that the concurrent DML operation on the partition table will not be blocked during the current deletion partition process, and the DDL operation on the partition table is avoided during the deletion partition process.

[0049] Specifically, the partition state protection lock includes but is not limited to a metadata lock of SHARED_NO_READ_WRITE level of My Structured Query Language (My Structured Query Language, MySQL) database, a table-level lock (Table-level lock, TM) of Oracle database, etc.

[0050] Referring to Figure 2At this time, the whole step of deleting the partition can be expressed as:

[0051] Step S201, starting a first transaction;

[0052] Step S202, setting a partition state protection lock for the partition table corresponding to the target partition;

[0053] Step S203, modifying the partition state corresponding to the target partition from the normal use state to a deleting state;

[0054] Step S204, committing the first transaction;

[0055] Step S205, starting a second transaction;

[0056] Step S206, waiting for all other transactions currently accessing the target partition to end;

[0057] Step S207, performing a metadata deletion operation;

[0058] Step S208, modifying the partition state corresponding to the target partition from the deleting state to a deleted state after the metadata deletion operation succeeds;

[0059] Step S209, committing the second transaction.

[0060] Preferably, the method described above further comprises:

[0061] If it is detected that the metadata deletion operation of the target partition fails, the second transaction is performed again on the target partition according to a preset cleanup partition syntax.

[0062] In this embodiment, the execution result is detected or received when the second transaction is performed. When the metadata deletion operation fails due to an exception when the second transaction is performed, the second transaction is performed again on the target partition according to the preset cleanup partition syntax to perform deletion again, so as to ensure the partition deletion effect. Specifically, the syntax module is expanded to add a new syntax function, that is, the preset cleanup partition syntax (CLEANUP PARTITION) in this embodiment. This syntax command is specially used for processing partitions that fail to complete the deletion process in the second transaction due to concurrent transaction conflicts and other exceptions, and separately performs the cleanup work of the partition. The syntax function is used to ensure the consistency and integrity of the database, and data inconsistency caused by the failure of the second transaction to perform online deletion of the partition does not occur.

[0063] In a specific embodiment, the preset cleanup partition syntax can be expressed as:

[0064] CLEANUP PARTITION table_name(partition_name).

[0065] Wherein, the table_name is the name of the partition table containing the target partition, and the partition_name is the name of the target partition to be cleaned up.

[0066] Specifically, the method as described above, the second transaction is executed again on the target partition according to the preset cleanup partition syntax further comprises:

[0067] Before the metadata deletion operation is executed, an exclusive deletion lock for ensuring atomicity of the metadata operation is set for the partition table corresponding to the target partition;

[0068] After the metadata deletion operation is executed, all locks corresponding to the partition table are released.

[0069] In this embodiment, when the second transaction is executed again on the target partition, in order to avoid the failure of the metadata deletion operation when the second transaction is executed due to the lack of locking when the first transaction or the second transaction is executed, an exclusive deletion lock for ensuring atomicity of the metadata operation is set for the partition table corresponding to the target partition before the metadata deletion operation is executed again, and then the metadata deletion operation is executed, and after the metadata deletion operation is executed, all locks corresponding to the partition table are released, wherein the all locks include the exclusive deletion lock applied this time and / or the partition state protection lock applied when the first transaction is executed.

[0070] In a specific embodiment, the exclusive deletion lock includes but is not limited to MDL_EXCLUSIVE exclusive metadata lock of MySQL database, DDL lock of Oracle database, etc.

[0071] Based on the above operation, in a specific embodiment, the preset cleanup partition syntax can be represented as:

[0072] CLEANUP PARTITION table_name(partition_name);

[0073] WITH LOCK TABLESPACE.

[0074] Wherein, the table_name is the name of the partition table containing the target partition, and the partition_name is the name of the target partition to be cleaned up, and the WITH LOCK TABLESPACE is used to instruct the system to lock the entire table space during the cleanup process, thereby ensuring that no other concurrent operation affects the consistency of the partition data during the cleanup operation.

[0075] Referring to Figure 3 At this time, the step of performing the second transaction on the target partition again according to the preset partition deletion syntax can be represented as:

[0076] In step S301, wait until all other transactions accessing the target partition are ended;

[0077] In step S302, lock the table space by an exclusive delete lock;

[0078] In step S303, perform a metadata deletion operation;

[0079] In step S304, after the metadata deletion operation is successful, modify the partition state corresponding to the target partition from the deleting state to the deleted state;

[0080] In step S305, release all locks corresponding to the partition table;

[0081] In step S306, commit the transaction.

[0082] Preferably, the method described above further comprises:

[0083] When performing a DDL operation on the partition table corresponding to the target partition, if it is detected that the target partition is in the deleting state, preset error information corresponding thereto is fed back.

[0084] In this embodiment, when a database performs a DDL operation on a partition table in which a target partition is located, if it is detected that the target partition is in the deleting state, it is determined that there is another deleted partition causing the target partition to be in the deleting state and that the first transaction has been completed. Since all transactions accessing the deleted partition cannot be ended, in order to guarantee data consistency, the DDL operation on the partition in this state is prevented, and therefore preset error information corresponding thereto is fed back to the user to feed back this information to the user.

[0085] Preferably, the method described above further comprises:

[0086] When performing an operation of obtaining a valid partition list in a DML operation on the partition table corresponding to the target partition, if it is detected that the target partition is in the deleting state, the target partition is skipped.

[0087] In this embodiment, when a database performs a DML operation on a partition table in which a target partition is located, in an operation step of obtaining a valid partition list, if it is detected that the target partition is in the deleting state, it is determined that the target partition is not suitable for performing a new DML operation, and therefore the target partition is skipped and the DML operation is continued to be performed on other partitions, so that it is guaranteed that the DML operation on other partitions is not blocked when the target partition is deleted, and therefore the concurrency performance of the DML operation when the partition is deleted is improved.

[0088] That is, the module for obtaining the partition when the query is expanded, and the first transaction for setting the partition state to the deleting state is submitted, and the concurrent DML transaction started is detected to be in the deleting state, and the valid partition list is obtained by skipping the partition.

[0089] Referring to Figure 4 Another embodiment of the present application provides a control device, comprising:

[0090] The first processing module 401 is configured to execute a first transaction on a target partition in a normal use state according to a partition deletion instruction, the first transaction comprising modifying a partition state corresponding to the target partition from the normal use state to a deleting state, the deleting state being used to indicate that no new data definition language (DDL) operation and data manipulation language (DML) operation is performed;

[0091] The second processing module 402 is configured to detect that the first transaction is submitted, and execute a second transaction on the target partition, the second transaction comprising executing a metadata deletion operation if it is detected that all other transactions currently accessing the target partition are ended, and modifying the partition state corresponding to the target partition from the deleting state to a deleted state after the metadata deletion operation is successful.

[0092] Preferably, the control device described above further comprises:

[0093] The third processing module is configured to, when the first transaction is executed, further set a partition state protection lock for isolating concurrent structure changes on a partition table corresponding to the target partition;

[0094] The fourth processing module is configured to, when the second transaction is executed, further release the partition state protection lock after the metadata deletion operation is successful.

[0095] Preferably, the control device described above further comprises:

[0096] The fifth processing module is configured to, if it is detected that the metadata deletion operation of the target partition fails, execute the second transaction again on the target partition according to a preset clear partition syntax.

[0097] Specifically, the method described above further comprises:

[0098] The first processing unit is configured to, before the metadata deletion operation is executed, set an exclusive deletion lock for guaranteeing atomicity of metadata operations on a partition table corresponding to the target partition;

[0099] The second processing unit is configured to, after the metadata deletion operation is executed, release all locks corresponding to the partition table.

[0100] Preferably, the control device as described above further comprises:

[0101] The sixth processing module is configured to, when performing a DDL operation on the partition table corresponding to the target partition, if it is detected that the target partition is in the deleting state, feed back corresponding preset error information.

[0102] Preferably, the control device as described above further comprises:

[0103] The seventh processing module is configured to, when performing an operation of obtaining a list of valid partitions in a DML operation on the partition table corresponding to the target partition, if it is detected that the target partition is in the deleting state, skip the target partition.

[0104] It should be noted that the control device in this embodiment is a device corresponding to the method of online deleting database partition, and the implementation manners in the above embodiments are applicable to the embodiment of the control device and can achieve the same technical effects. The control device provided in the embodiments of the present application can implement all the method steps achieved by the method embodiments and can achieve the same technical effects. Therefore, the same parts and beneficial effects in the embodiment and the method embodiments will not be described in detail.

[0105] Another embodiment of the present application provides an electronic device, which comprises a processor, a memory, and a program stored in the memory and executable on the processor. When the program is executed by the processor, the steps of the method of online deleting database partition are implemented, and the same technical effects can be achieved. Therefore, the same parts and beneficial effects in the embodiment and the method embodiments will not be described in detail.

[0106] Still another embodiment of the present application provides a computer readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps of the method of online deleting database partition are implemented, and the same technical effects can be achieved. Therefore, the same parts and beneficial effects in the embodiment and the method embodiments will not be described in detail. The computer readable storage medium can be a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0107] Still another embodiment of the present application provides a computer program product comprising computer instructions which, when executed by a processor, implement the steps of the method for online deleting database partition as described above, and can achieve the same technical effects, and here the same parts and beneficial effects of the method embodiment in this embodiment will not be described in detail.

[0108] Through the above description of the embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment method can be realized by means of software and a necessary general hardware platform, of course, it can also be realized by hardware, but in many cases the former is a better embodiment. Based on such understanding, the technical solutions of the present application can be embodied in the form of a software product in essence or in the form of a part of the prior art. The computer software product is stored in a storage medium (such as a ROM / RAM, a magnetic disk, an optical disk), and includes a plurality of instructions for causing a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the method described in each embodiment of the present application.

[0109] The embodiments of the present application are described above in combination with the drawings, but the present application is not limited to the above-mentioned specific embodiments, and the above-mentioned specific embodiments are only illustrative, not restrictive. Those skilled in the art can make many forms under the inspiration of the present application without departing from the scope of the present application and the scope of protection of the claims.

Claims

1. A method of online deletion of a database partition, characterized by, The method comprises the following steps: According to the partition deletion instruction, a first transaction is executed on a target partition in a normal use state corresponding to the partition deletion instruction, and the first transaction comprises modifying a partition state corresponding to the target partition from the normal use state to a deleting state, wherein the deleting state is used to indicate that no new data definition language (DDL) operation and data manipulation language (DML) operation is executed; After detecting that the first transaction is submitted, a second transaction is executed on the target partition, and the second transaction comprises executing a metadata deletion operation if it is detected that all other transactions currently accessing the target partition are ended, and modifying the partition state corresponding to the target partition from the deleting state to a deleted state after the metadata deletion operation is successful.

2. The method of claim 1, wherein, The method further comprises the following steps: When the first transaction is executed, a partition state protection lock for isolating concurrent structure changes is further set for a partition table corresponding to the target partition; When the second transaction is executed, the partition state protection lock is released after the metadata deletion operation is successful.

3. The method according to claim 1 or 2, characterized in that, The method further comprises the following steps: If it is detected that the metadata deletion operation of the target partition fails, the second transaction is executed again on the target partition according to a preset clear partition syntax.

4. The method of claim 3, wherein, The step of executing the second transaction again on the target partition according to the preset clear partition syntax further comprises the following steps: Before the metadata deletion operation is executed, an exclusive deletion lock for guaranteeing atomicity of the metadata operation is set for a partition table corresponding to the target partition; After the metadata deletion operation is executed, all locks corresponding to the partition table are released.

5. The method of claim 1, wherein, The method further comprises the following steps: When a DDL operation is executed on a partition table corresponding to the target partition according to a partition DDL operation instruction, if it is detected that the target partition is in the deleting state, preset error information corresponding to the target partition is fed back.

6. The method of claim 1, wherein, The method further comprises the following steps: When a get valid partition list operation in a DML operation is executed on a partition table corresponding to the target partition according to a partition DML operation instruction, if it is detected that the target partition is in the deleting state, the target partition is skipped.

7. A control device characterized by comprising: The method comprises the following steps: A first processing module is configured to execute a first transaction on a target partition in a normal use state corresponding to a partition deletion instruction according to the partition deletion instruction, and the first transaction comprises modifying a partition state corresponding to the target partition from the normal use state to a deleting state, wherein the deleting state is used to indicate that no new data definition language (DDL) operation and data manipulation language (DML) operation is executed; A second processing module is configured to execute a second transaction on the target partition after detecting that the first transaction is submitted, and the second transaction comprises executing a metadata deletion operation if it is detected that all other transactions currently accessing the target partition are ended, and modifying the partition state corresponding to the target partition from the deleting state to a deleted state after the metadata deletion operation is successful.

8. An electronic device, comprising: The method comprises the following steps: A processor, a memory, and a program stored on the memory and executable on the processor are provided, and the program is executed by the processor to implement the steps of the method for online deleting a database partition according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the method of online deletion of database partitions according to any one of claims 1 to 6.

10. A computer program product, characterised in that, The computer program product comprises computer instructions which, when executed by a processor, implement the steps of the method of online deletion of database partitions according to any one of claims 1 to 6.

Images