CN118796805A - Method, device, electronic device and storage medium for realizing data row identification function - Google Patents

Abstract

The invention provides a method, a device, an electronic device and a storage medium for realizing a data line identification function, which are applied to a PostgreSQL database server and comprise the following steps: under the condition that a data line identifier ROWID application initiated by a service application system is received, pulling the next value of the self-increasing sequence in ROWID from the shared memory; and returning the next value of the self-increasing sequence in ROWID to the service application system so that the service application system can update or delete the data table record according to the next value of the self-increasing sequence in ROWID. The invention can realize ROWID functions similar to the Oracle database based on the self-increasing sequence in the PostgreSQL database, and solves the problem of large workload of application code transformation when an application system is switched from the Oracle database to the PostgreSQL database and the problem of change of citd of the table record after update.

Description

Method, device, electronic device and storage medium for realizing data row identification function

Technical Field

The present invention relates to the field of computer technology, and in particular to a method, device, electronic device and storage medium for implementing a data row identification function.

Background Art

With the continuous development of science and technology, the autonomy and controllability of Internet technology (IT) systems have received more and more attention. The autonomy and controllability of databases is a key link in the autonomy and controllability of IT systems. Currently, Oracle databases account for the largest proportion of databases used in various industries, and are gradually switching to domestic databases and open source databases.

The most mainstream open source databases are PostgreSQL and MySQL. Currently, Oracle databases in various industries are mainly switched to domestic databases based on PostgreSQL or MySQL, PostgreSQL open source databases, and MySQL open source databases. The row identifier ROWID is a system field in the Oracle database. It can be used to uniquely identify the physical location of a record in the database table and is globally unique. Therefore, ROWID is widely used in business application systems to update or delete data table records to improve efficiency.

However, the PostgreSQL database does not provide a ROWID system field, but only a ctid system field with similar functions. Therefore, when the application system is switched from an Oracle database to a PostgreSQL database, if the ROWID function of the Oracle database is used in the application code, due to the difference in the multiversion concurrency control mechanism (Multiversion Concurrency Control, MVCC) between the Oracle database and the PostgreSQL database, the ctid of the data row will change after the data row in the PostgreSQL database is updated; and if the ctid is updated multiple times in a transaction, it will cause industrial business logic errors.

Therefore, how to implement the data row identification ROWID function of the PostgreSQL database is a problem that needs to be solved urgently.

Summary of the invention

In view of the problems existing in the prior art, the present invention provides a method for implementing a data row identification function, which is applied to a PostgreSQL database server, comprising:

When receiving a data row ID ROWID request initiated by the business application system, pull the next value in the auto-increment sequence of ROWID from the shared memory;

The next value of the self-increment sequence in the ROWID is returned to the business application system, so that the business application system updates or deletes the data table record according to the next value of the self-increment sequence in the ROWID.

According to a method for implementing a data row identification function provided by the present invention, after pulling the next value of the auto-increment sequence in the ROWID from the shared memory, the method further includes:

If the current transaction is not committed, write the next value of the auto-increment sequence in the ROWID to the log file and disk;

When the database is restarted, the next value of the auto-increment sequence in the ROWID is loaded from the log file into the shared memory.

According to a method for implementing a data row identification function provided by the present invention, the step of writing the next value of the auto-increment sequence in the ROWID into a log file and a disk comprises:

Persist the next value of the auto-increment sequence in the ROWID to the log file, and determine whether to perform a data persistence operation;

When performing a data persistence operation, the next value of the auto-increment sequence in the ROWID is persisted to the disk.

According to a method for implementing a data row identification function provided by the present invention, persisting the next value of the auto-increment sequence in the ROWID to a log file includes:

If the next value of the auto-increment sequence in the ROWID being written to the log file is greater than the maximum ROWID value applied by the current transaction, the next value of the auto-increment sequence in the ROWID is not written to the log file again;

When the next value of the auto-increment sequence in the ROWID being written to the log file is less than or equal to the maximum value applied by the current transaction, the next value of the auto-increment sequence in the ROWID is written to the log file, and the log writing status is recorded in the shared memory.

According to a method for implementing a data row identification function provided by the present invention, after writing the next value of the auto-increment sequence in the ROWID to a log file and a disk when the current transaction is not committed, the method further includes:

When the current transaction has been committed, the next value of the auto-increment sequence in the ROWID that has been written into the log file is recorded in the shared memory.

According to a method for implementing a data row identification function provided by the present invention, the step of pulling the next value of the auto-increment sequence in the ROWID from the shared memory includes:

Use atomic operations or spin lock mode to pull the next value in the self-increment sequence in ROWID from shared memory.

According to a method for implementing a data row identification function provided by the present invention, returning the next value of the auto-increment sequence in the ROWID to the business application system includes:

Using an encryption algorithm to encrypt the next value of the self-increment sequence in the ROWID to obtain encrypted data;

The encrypted data is returned to the business application system.

The present invention also provides a device for implementing a data row identification function, which is applied to a PostgreSQL database server and includes:

The pull module is used to pull the next value of the auto-increment sequence in the ROWID from the shared memory when receiving the data row identifier ROWID request initiated by the business application system;

The return module is used to return the next value of the auto-increment sequence in the ROWID to the business application system, so that the business application system updates or deletes the data table record according to the next value of the auto-increment sequence in the ROWID.

The present invention also provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the steps of the method for implementing the data row identification function as described in any one of the above items are implemented.

The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of the method for implementing the data row identification function as described in any one of the above items are implemented.

In the embodiment of the present invention, when a PostgreSQL database server receives a data row identifier ROWID application initiated by a business application system, the server pulls the next value of the auto-increment sequence in the ROWID from the shared memory; returns the next value of the auto-increment sequence in the ROWID to the business application system, so that the business application system updates or deletes the data table record according to the next value of the auto-increment sequence in the ROWID, thereby realizing a ROWID function similar to that of the Oracle database based on the auto-increment sequence in the PostgreSQL database, so that the ROWID of the PostgreSQL database is fully compatible with the ROWID of the Oracle database. Compared with the existing ctid solution, on the one hand, it solves the problem of large workload of application code transformation when the application system switches from the Oracle database to the PostgreSQL database; on the other hand, after the data table record is updated, the ROWID of the table record remains unchanged, which will not cause the failure of the second ROWID-based update in the transaction and has no impact on the business, thereby solving the problem of the citd of the table record changing after the update.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions in the present invention or the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

FIG1 is a schematic diagram of a second ctid-based update failure in a transaction in the prior art;

2 is a schematic flow chart of a method for implementing a data row identification function provided by an embodiment of the present invention;

3 is a schematic diagram of the physical structure of a data row identifier ROWID provided in an embodiment of the present invention;

FIG4 is a schematic diagram of a ROWID generation process according to an embodiment of the present invention;

FIG5 is an overall architecture diagram of a ROWID application provided in an embodiment of the present invention;

6 is a schematic diagram of the structure of a device for implementing a data row identification function provided by an embodiment of the present invention;

FIG. 7 is a schematic diagram of the structure of an electronic device provided by an embodiment of the present invention.

DETAILED DESCRIPTION

In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be clearly and completely described below in conjunction with the drawings of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

The ctid system field of the PostgreSQL database is similar to the ROWID system field. Both are used to locate the physical location of a record in the database. However, the ctid system field of the table data will change after the table data is updated. The fundamental reason for the change in the ctid system field is the difference in the multi-version concurrency control mechanism (MVCC) between the PostgreSQL database and the Oracle database. The MVCC mechanism of the Oracle database is implemented through the undo tablespace. When the table data is updated, the old version of the data will be stored in the undo tablespace. The MVCC mechanism of the PostgreSQL database does not have an undo tablespace. When the table data is updated, the old version of the data still exists on the old data block, but the old version of the record is marked as unavailable, and then the updated new version of the data is inserted into another position of the data block, resulting in a change in the physical location of the table data, and the ctid system field changes accordingly.

However, the ROWID function implemented through the ctid system field has the following two problems:

(1) Application code needs to be modified, which requires a lot of work: The PostgreSQL database does not provide the ROWID function. When the application system is switched from the Oracle database to the PostgreSQL database, the application code needs to be modified. The SQL code that searches based on ROWID in the application code needs to be modified to search based on ctid, which greatly increases the workload of the application system modification.

(2) The second update based on ctid in a transaction fails: Figure 1 is a schematic diagram of the second update based on ctid in a transaction in the prior art. Referring to Figure 1, when the table data is updated multiple times based on the same ctid system field in the same transaction, due to the MVCC mechanism of the PostgreSQL database, the ctid of the table data will change after the first update, resulting in the failure to find the corresponding record when the ctid is subsequently updated again, thereby causing business logic anomalies and affecting the business.

The core concept of the embodiment of the present invention is to implement a ROWID function similar to that of an Oracle database based on an auto-increment sequence in a PostgreSQL database, so that the ROWID of the PostgreSQL database is fully compatible with the ROWID of the Oracle database. Compared with the existing ctid solution, on the one hand, it solves the problem of heavy workload of application code transformation when the application system switches from an Oracle database to a PostgreSQL database; on the other hand, after the data table record is updated, the ROWID of the table record remains unchanged, which will not cause the second ROWID-based update failure in the transaction and has no impact on the business, thereby solving the problem of the citd of the table record changing after the update.

Fig. 2 is a flow chart of a method for implementing a data row identification function provided by an embodiment of the present invention. Referring to Fig. 2, an embodiment of the present invention provides a method for implementing a data row identification function, which is applied to a PostgreSQL database server. The method may specifically include the following steps:

Step 201, when receiving a data row identifier ROWID request initiated by a business application system, pull the next value of the auto-increment sequence in the ROWID from the shared memory.

The implementation method of the data row identification function provided by the embodiment of the present invention can be applied to a PostgreSQL database server. The business application system can initiate a ROWID request. The PostgreSQL database server can pull the next value of the auto-increment sequence in the ROWID from the shared memory and return the next value of the auto-increment sequence to the business application system, thereby implementing the data row identification ROWID function of the PostgreSQL database.

When the business application system initiates a Structured Query Language (SQL) operation, the PostgreSQL database engine can initiate SQL parsing. When the parsing result is a data insertion operation, that is, a data row identifier ROWID application, the latest ROWID can be pulled from the shared memory.

Fig. 3 is a schematic diagram of the physical structure of a data row identifier ROWID provided by an embodiment of the present invention. Referring to Fig. 3, ROWID can be represented by a 64-bit unsigned integer, and ROWID can be composed of "high N bits" and "low N bits", "high N bits" can represent an object ID (Identity Document, identity identification), and "low N bits" can represent a self-incrementing sequence.

Specifically, when calling the auto-increment sequence in ROWID, the nextval method can be used to obtain the next value of the sequence. Each time the nextval method is called, the sequence can be automatically incremented and return the next value generated. In an embodiment of the present invention, the next value of the auto-increment sequence in ROWID can be represented by next ROWID.

The "low N bits" of the row ID ROWID can use the global session variable (Global Unified Configuration variable, GUC) default_with_rowid_id, and the data bit can be increased by 1 each time and saved in the shared memory. Each time the business application system requests a new ROWID value, the next ROWID value in the shared memory can be updated (using a spin lock for protection), thereby ensuring that the previous duplicate value will not be generated after the service is restarted.

In the embodiment of the present invention, the ROWID field can be set as a virtual column, which cannot be changed or specified by the user.

Step 202: Return the next value of the auto-increment sequence in the ROWID to the business application system, so that the business application system updates or deletes the data table record according to the next value of the auto-increment sequence in the ROWID.

After the PostgreSQL database server pulls the next value of the auto-increment sequence in the ROWID from the shared memory, it can return the next value of the auto-increment sequence in the ROWID to the business application system that initiated the ROWID request, so that the business application system can update or delete data table records according to the next value of the auto-increment sequence.

In the embodiment of the present invention, when a PostgreSQL database server receives a data row identifier ROWID application initiated by a business application system, the server pulls the next value of the auto-increment sequence in the ROWID from the shared memory; returns the next value of the auto-increment sequence in the ROWID to the business application system, so that the business application system updates or deletes the data table record according to the next value of the auto-increment sequence in the ROWID, thereby realizing a ROWID function similar to that of the Oracle database based on the auto-increment sequence in the PostgreSQL database, so that the ROWID of the PostgreSQL database is fully compatible with the ROWID of the Oracle database. Compared with the existing ctid solution, on the one hand, it solves the problem of large workload of application code transformation when the application system switches from the Oracle database to the PostgreSQL database; on the other hand, after the data table record is updated, the ROWID of the table record remains unchanged, which will not cause the failure of the second ROWID-based update in the transaction and has no impact on the business, thereby solving the problem of the citd of the table record changing after the update.

In an optional embodiment, after pulling the next value of the auto-increment sequence in the ROWID from the shared memory, it also includes: when the current transaction is not committed, writing the next value of the auto-increment sequence in the ROWID to the log file and disk; when the database is restarted, loading the next value of the auto-increment sequence in the ROWID from the log file to the shared memory.

FIG4 is a schematic diagram of a ROWID generation process provided by an embodiment of the present invention. Referring to FIG4, in a business application system, business A can initiate a ROWID application, business B can initiate a ROWID application, and business X can initiate a ROWID application. The nextval method can be called to obtain the next value of the auto-increment sequence in the ROWID from the shared memory, and determine whether the current transaction has been committed. If the current transaction is not committed, the next value of the auto-increment sequence in the ROWID obtained from the shared memory can be written to the write-ahead log (WAL) and the disk.

In the case of abnormal database downtime or database restart, the PostgreSQL database can be restored based on the WAL log file and load the latest ROWID information (that is, the next value in the auto-increment sequence of the latest ROWID) into the shared memory to ensure that the obtained ROWID is the latest. Each restart can obtain the largest next ROWID value (that is, the next value in the auto-increment sequence of ROWID) from the log file and replace the value in the shared memory.

In an optional embodiment, writing the next value of the auto-increment sequence in the ROWID to a log file and a disk includes: persisting the next value of the auto-increment sequence in the ROWID to a log file, and determining whether to perform a data persistence operation; and if performing a data persistence operation, persisting the next value of the auto-increment sequence in the ROWID to a disk.

Please continue to refer to FIG. 4. In actual applications, the data persistence operation may refer to a checkpoint operation. If the current transaction is not committed, the next value of the auto-increment sequence may be persisted to a log file, and it is determined whether to perform a checkpoint operation. If a checkpoint operation is performed, the next value of the auto-increment sequence may be persisted to a disk.

In the embodiment of the present invention, the next ROWID may be saved each time a checkpoint is performed so that the next value can be restored after the service is restarted.

In an optional embodiment, persisting the next value of the auto-increment sequence in the ROWID to the log file includes: when the next value of the auto-increment sequence in the ROWID being written to the log file is greater than the maximum ROWID value applied for the current transaction, not writing the next value of the auto-increment sequence in the ROWID to the log file again; when the next value of the auto-increment sequence in the ROWID being written to the log file is less than or equal to the maximum value applied for the current transaction, writing the next value of the auto-increment sequence in the ROWID to the log file, and recording the log writing status in the shared memory.

In the embodiment of the present invention, ROWID log optimization can be performed. Specifically, in order to reduce the number of log writing, a single process can record the ROWID it applied for last, and before writing the log, it can compare whether the next ROWID being written or written to the WAL log file (i.e., the next value in the auto-increment sequence in the ROWID) is greater than the maximum ROWID value applied for by the current transaction.

If the next ROWID that is being written or has been written to the WAL log file is greater than the maximum ROWID value requested by this transaction, there is no need to write to the WAL log file again.

If the next ROWID being written or already written to the WAL log file is less than or equal to the maximum ROWID value requested by this transaction, the next ROWID in the shared memory can be taken and written to the WAL log file, and the shared memory is recorded as being written to the WAL log file.

In an embodiment of the present invention, the ROWID sequence is written to the WAL log file each time, but forced writing to disk may not be performed because the disk is forced to be written when the transaction is committed, and there will be no conflict even if it is rolled back and reused. After restarting, the maximum ROWID value in the WAL log file can be retained and restored to the shared memory.

In an optional embodiment, after writing the next value of the auto-increment sequence in the ROWID to the log file and the disk when the current transaction is not committed, it also includes: when the current transaction is committed, recording in the shared memory the next value of the auto-increment sequence in the ROWID that has been written to the log file.

Please continue to refer to Figure 4. When the current transaction is not committed, the next value of the auto-increment sequence in ROWID is written to the log file and disk, and the WAL log file is recorded in the shared memory. If the current transaction is committed, the next ROWID (that is, the next value of the auto-increment sequence in ROWID) written to the WAL log file can be recorded in the shared memory.

In an optional embodiment, pulling the next value of the self-increment sequence in the ROWID from the shared memory includes: using an atomic operation or a spin lock mode to pull the next value of the self-increment sequence in the ROWID from the shared memory.

In an embodiment of the present invention, a data row identifier ROWID sequence is stored in a shared memory. In the process of pulling ROWID from the shared memory, atomic operations or spin locks can be used to resolve conflicts, thereby avoiding the problem of resource contention when concurrently applying for ROWID.

In an optional embodiment, returning the next value of the self-increment sequence in the ROWID to the business application system includes: encrypting the next value of the self-increment sequence in the ROWID using an encryption algorithm to obtain encrypted data; and returning the encrypted data to the business application system.

In the embodiment of the present invention, ROWID is composed of object ID + auto-increment sequence. Each time after the next value of the auto-increment sequence is obtained from the shared memory, an encryption algorithm can be used to encrypt it to obtain encrypted data and return the encrypted data to the business application.

Fig. 5 is an overall architecture diagram of the ROWID application provided by an embodiment of the present invention. Referring to Fig. 5, a ROWID generation center virtual module may be set, and the ROWID generation virtual module may be composed of a ROWID generation unit and a ROWID persistence unit. When the business application system initiates an SQL operation, the database engine may perform SQL parsing and judgment.

When data insertion is involved, you can apply for ROWID from the ROWID generation center virtual module. The ROWID generation unit can pull the latest ROWID from the shared memory. During the ROWID pulling process, the spin lock mode can be used to avoid resource contention when concurrently applying for ROWID; the ROWID persistence unit can write the latest ROWID in the shared memory to the WAL log file and disk, which is initiated when the transaction is committed or the checkpoint is executed.

When the database crashes abnormally or is restarted, the PostgreSQL database can recover based on the WAL log file and load the latest ROWID information into the shared memory, thus ensuring that the obtained ROWID is the latest.

In the embodiment of the present invention, when a PostgreSQL database server receives a data row identifier ROWID application initiated by a business application system, the server pulls the next value of the auto-increment sequence in the ROWID from the shared memory; returns the next value of the auto-increment sequence in the ROWID to the business application system, so that the business application system updates or deletes the data table record according to the next value of the auto-increment sequence in the ROWID, thereby realizing a ROWID function similar to that of the Oracle database based on the auto-increment sequence in the PostgreSQL database, so that the ROWID of the PostgreSQL database is fully compatible with the ROWID of the Oracle database. Compared with the existing ctid solution, on the one hand, it solves the problem of large workload of application code transformation when the application system switches from the Oracle database to the PostgreSQL database; on the other hand, after the data table record is updated, the ROWID of the table record remains unchanged, which will not cause the failure of the second ROWID-based update in the transaction and has no impact on the business, thereby solving the problem of the citd of the table record changing after the update.

The following describes an implementation device for the data row identification function provided by the present invention. The implementation device for the data row identification function described below and the implementation method for the data row identification function described above can refer to each other.

FIG6 is a schematic diagram of the structure of a device for implementing a data row identification function provided by an embodiment of the present invention. Referring to FIG6 , an embodiment of the present invention provides a device for implementing a data row identification function, and the device may specifically include the following modules:

The pulling module 601 is used to pull the next value of the auto-increment sequence in the ROWID from the shared memory when receiving a data row identifier ROWID request initiated by the business application system;

The return module 602 is used to return the next value of the auto-increment sequence in the ROWID to the business application system, so that the business application system updates or deletes the data table record according to the next value of the auto-increment sequence in the ROWID.

In an optional embodiment, after pulling the next value of the auto-increment sequence in the ROWID from the shared memory, the method further includes:

A writing module, used for writing the next value of the auto-increment sequence in the ROWID into a log file and a disk when the current transaction is not committed;

A loading module is used to load the next value of the auto-increment sequence in the ROWID from the log file into the shared memory when the database is restarted.

In an optional embodiment, the writing module includes:

The log writing submodule is used to persist the next value of the auto-increment sequence in the ROWID to the log file and determine whether to perform the data persistence operation;

The disk writing submodule is used to persist the next value of the auto-increment sequence in the ROWID to the disk when performing a data persistence operation.

In an optional embodiment, the log writing submodule includes:

a non-writing unit, configured to not write the next value of the self-increment sequence in the ROWID being written into the log file again if the next value of the self-increment sequence in the ROWID being written into the log file is greater than the maximum ROWID value applied by the current transaction;

A status recording unit is used to write the next value of the self-increment sequence in the ROWID being written to the log file and record the log writing status in the shared memory when the next value of the self-increment sequence in the ROWID being written to the log file is less than or equal to the maximum value applied by the current transaction.

In an optional embodiment, after writing the next value of the auto-increment sequence in the ROWID to the log file and the disk when the current transaction is not committed, the method further includes:

The memory recording module is used to record in the shared memory the next value of the auto-increment sequence in the ROWID that has been written into the log file when the current transaction has been committed.

In an optional embodiment, the pulling module includes:

The spin lock pull submodule is used to pull the next value of the self-increment sequence in ROWID from the shared memory using atomic operations or spin lock mode.

In an optional embodiment, the loading module includes:

An encryption submodule, used for encrypting the next value of the self-increment sequence in the ROWID using an encryption algorithm to obtain encrypted data;

The data return submodule is used to return the encrypted data to the business application system.

In the embodiment of the present invention, when a PostgreSQL database server receives a data row identifier ROWID application initiated by a business application system, the server pulls the next value of the auto-increment sequence in the ROWID from the shared memory; returns the next value of the auto-increment sequence in the ROWID to the business application system, so that the business application system updates or deletes the data table record according to the next value of the auto-increment sequence in the ROWID, thereby realizing a ROWID function similar to that of the Oracle database based on the auto-increment sequence in the PostgreSQL database, so that the ROWID of the PostgreSQL database is fully compatible with the ROWID of the Oracle database. Compared with the existing ctid solution, on the one hand, it solves the problem of large workload of application code transformation when the application system switches from the Oracle database to the PostgreSQL database; on the other hand, after the data table record is updated, the ROWID of the table record remains unchanged, which will not cause the failure of the second ROWID-based update in the transaction and has no impact on the business, thereby solving the problem of the citd of the table record changing after the update.

FIG7 illustrates a schematic diagram of the physical structure of an electronic device. As shown in FIG7 , the electronic device may include: a processor 710, a communications interface 720, a memory 730, and a communication bus 740, wherein the processor 710, the communications interface 720, and the memory 730 communicate with each other through the communication bus 740. The processor 710 may call the logic instructions in the memory 730 to execute a method for implementing a data row identification function, and the method includes:

When receiving a data row ID ROWID request initiated by the business application system, pull the next value in the auto-increment sequence of ROWID from the shared memory;

The next value of the self-increment sequence in the ROWID is returned to the business application system, so that the business application system updates or deletes the data table record according to the next value of the self-increment sequence in the ROWID.

In addition, the logic instructions in the above-mentioned memory 730 can be implemented in the form of a software functional unit and can be stored in a computer-readable storage medium when it is sold or used as an independent product. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

In another aspect, the present invention further provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a method for implementing the data row identification function provided by the above methods, the method comprising:

When receiving a data row ID ROWID request initiated by the business application system, pull the next value in the auto-increment sequence of ROWID from the shared memory;

The next value of the self-increment sequence in the ROWID is returned to the business application system, so that the business application system updates or deletes the data table record according to the next value of the self-increment sequence in the ROWID.

The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.

Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM/RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims (10)

1. A method for implementing a data row identification function, characterized in that it is applied to a PostgreSQL database server, comprising: When receiving a data row ID ROWID request initiated by the business application system, pull the next value in the auto-increment sequence of ROWID from the shared memory; The next value of the self-increment sequence in the ROWID is returned to the business application system, so that the business application system updates or deletes the data table record according to the next value of the self-increment sequence in the ROWID. 2. The method according to claim 1, characterized in that after pulling the next value of the auto-increment sequence in the ROWID from the shared memory, it also includes: If the current transaction is not committed, write the next value of the auto-increment sequence in the ROWID to the log file and disk; When the database is restarted, the next value of the auto-increment sequence in the ROWID is loaded from the log file into the shared memory. 3. The method according to claim 2, wherein the step of writing the next value of the auto-increment sequence in the ROWID to a log file and a disk comprises: Persist the next value of the auto-increment sequence in the ROWID to the log file, and determine whether to perform a data persistence operation; When performing a data persistence operation, the next value of the auto-increment sequence in the ROWID is persisted to the disk. 4. The method according to claim 3, characterized in that persisting the next value of the auto-increment sequence in the ROWID to a log file comprises: If the next value of the auto-increment sequence in the ROWID being written to the log file is greater than the maximum ROWID value applied by the current transaction, the next value of the auto-increment sequence in the ROWID is not written to the log file again; When the next value of the auto-increment sequence in the ROWID being written to the log file is less than or equal to the maximum value applied by the current transaction, the next value of the auto-increment sequence in the ROWID is written to the log file, and the log writing status is recorded in the shared memory. 5. The method according to claim 2, characterized in that, after writing the next value of the auto-increment sequence in the ROWID to the log file and the disk when the current transaction is not committed, it also includes: When the current transaction has been committed, the next value of the auto-increment sequence in the ROWID that has been written into the log file is recorded in the shared memory. 6. The method according to claim 1, characterized in that the step of pulling the next value of the auto-increment sequence in the ROWID from the shared memory comprises: Use atomic operations or spin lock mode to pull the next value in the self-increment sequence in ROWID from shared memory. 7. The method according to claim 1, characterized in that the step of returning the next value of the auto-increment sequence in the ROWID to the business application system comprises: Using an encryption algorithm to encrypt the next value of the self-increment sequence in the ROWID to obtain encrypted data; The encrypted data is returned to the business application system. 8. A device for implementing a data row identification function, characterized in that it is applied to a PostgreSQL database server, comprising: The pull module is used to pull the next value of the auto-increment sequence in the ROWID from the shared memory when receiving the data row identifier ROWID request initiated by the business application system; The return module is used to return the next value of the self-increment sequence in the ROWID to the business application system, so that the business application system updates or deletes the data table record according to the next value of the self-increment sequence in the ROWID. 9. An electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method for implementing the data row identification function as described in any one of claims 1 to 7 when executing the program. 10. A non-transitory computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the method for implementing the data row identification function as described in any one of claims 1 to 7 is implemented.