WO2017101505A1 - Procédé de migration fondé sur un dispositif de mémorisation de blocs postgresql - Google Patents

Procédé de migration fondé sur un dispositif de mémorisation de blocs postgresql Download PDF

Info

Publication number
WO2017101505A1
WO2017101505A1 PCT/CN2016/096971 CN2016096971W WO2017101505A1 WO 2017101505 A1 WO2017101505 A1 WO 2017101505A1 CN 2016096971 W CN2016096971 W CN 2016096971W WO 2017101505 A1 WO2017101505 A1 WO 2017101505A1
Authority
WO
WIPO (PCT)
Prior art keywords
postgresql
block
postgresql block
data
storage device
Prior art date
Application number
PCT/CN2016/096971
Other languages
English (en)
Chinese (zh)
Inventor
朱晓伟
Original Assignee
深圳市华讯方舟软件技术有限公司
华讯方舟科技有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 深圳市华讯方舟软件技术有限公司, 华讯方舟科技有限公司 filed Critical 深圳市华讯方舟软件技术有限公司
Publication of WO2017101505A1 publication Critical patent/WO2017101505A1/fr

Links

Images

Classifications

    • 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/21—Design, administration or maintenance of databases
    • G06F16/217—Database tuning
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • 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/21—Design, administration or maintenance of databases
    • G06F16/214—Database migration support
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/061—Improving I/O performance
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0629—Configuration or reconfiguration of storage systems
    • G06F3/0631—Configuration or reconfiguration of storage systems by allocating resources to storage systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0638—Organizing or formatting or addressing of data
    • G06F3/0644—Management of space entities, e.g. partitions, extents, pools
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]

Definitions

  • the invention relates to a migration method of a PostgreSQL database storage device, in particular to a migration method based on a PostgreSQL block storage device.
  • the original PostgreSQL database system's underlying storage architecture is on the file system. From the table to the disk, the four layers of the tablespace, file system, logical volume, and disk are finally written to the physical disk.
  • the data manipulation of the database has several primary identifiers for each record.
  • Existing PostgreSQL database system read and write table operations need to:
  • Fsm file It stores information about the free space in the data table file.
  • Vm file A tuple that marks which file blocks in the data table file are not invalid.
  • Table data file This file is mainly used to store data, but the file size will be limited. Normally, 2G will be saved. Files larger than 2G will be saved in files.
  • the general operating system has a limit on the number of files that can be opened.
  • the PostgreSQL database system internally uses its own virtual file management to manage file handles to ensure that many tables can be opened at the same time. For the database, there may be many tables at the same time, and the PostgreSQL database system uses one table and multiple files to save data.
  • you open a file you will first find in the file handle management whether there is a file handle that has been opened. Set the offset according to the file handle.
  • centralized storage disk array, etc.
  • This method only hardly improves the I/O throughput of the back end, and does not improve the utilization of the underlying I/O in principle. And in terms of security, this method does not protect the data at any level, and still exposes the data. It can only achieve the speedup of the database system to a certain extent. But for the high security and high performance requirements, we can't just rely on this pure hardware acceleration and ignore the optimization of the software itself.
  • the above is the original PostgreSQL database system storage architecture.
  • the above structure has the following disadvantages:
  • the database is migrated between different systems and is complex, requiring high professional knowledge of the operators.
  • 64-bit space is used to record the number of blocks and the number of i-nodes.
  • 64-bit space is used to record the number of blocks and the number of i-nodes.
  • database systems there may be a large number of tables, and each table may have at least 3 files. , resulting in a lot of files in a folder.
  • the file system When the file system performs block allocation, it is basically allocated in a 4K block mode. At the same time, our database application is applied in 8K units. This means that the blocks allocated by the system are always smaller than the blocks of our table.
  • the direct problem with this is that the database's business blocks are cluttered to disk. The direct problem is that the disk seek time is long and the read and write speed is slowed down.
  • the database data files are directly exposed in the operating system, the data has security risks, and the data security is not guaranteed. It is a great security vulnerability for some environments with high security requirements.
  • the technical problem to be solved by the present invention is to provide a migration method based on a PostgreSQL block storage device, which migrates a database between different systems and is simple to the operator.
  • the professional knowledge of the staff is relatively high.
  • the present invention is based on a migration method of a PostgreSQL block storage device, which uses a PostgreSQL block storage device read/write module to read and write a PostgreSQL block, and the PostgreSQL block storage device read and write module passes between PostgreSQL blocks and data tables.
  • Mapping the relational table and the idle PostgreSQL block table to manage the PostgreSQL block in the PostgreSQL block storage device copying the mapping relationship table between the PostgreSQL block-data table and the free PostgreSQL block table from the original library to the new library,
  • the PostgreSQL block storage device is migrated from the computer where the original library resides to the computer where the new library resides.
  • the driver of the PostgreSQL block storage device read/write module completes the operation of the block file, and its main tasks are:
  • the table space is located to a specified position of the specified block device, and a certain offset of the block device is located by the pageid of the table.
  • Each table in the PostgreSQL database system is assigned at least one of the PostgreSQL blocks, and the PostgreSQL block can be dynamically allocated incrementally;
  • Each PostgreSQL block can write to 512 8-KB PostgreSQL block database system pages.
  • a block device can contain an infinite number of tables.
  • a table can contain an unlimited number of PostgreSQL blocks. These block file information is stored in PostgreSQL block-data. The mapping relationship between the tables;
  • the information of all the PostgreSQL blocks of a data table can be obtained by one oid, and the PostgreSQL block information will sequentially form the entire PostgreSQL block-data table file.
  • the pageid*8k of this table is the internal bias of the table. Move, and at the same time be able to determine the first block of this block file, and thus get the position of the page we want to get in the block device.
  • the first PostgreSQL block in the PostgreSQL storage device is allocated as a PostgreSQL block for authentication.
  • This block holds the unique verification code of the PostgreSQL database.
  • the verification code is 128-bit, in the case of cluster migration or database static recovery, you can obtain the data in the PostgreSQL database by providing a verification code to verify.
  • the PostgreSQL block storage device read and write module is architected on a PostgreSQL database system.
  • the mapping relationship table between the PostgreSQL block and the data table includes fields Relfilenode, Reltablespace, Forknum, Blockid, Blockno, and the free PostgreSQL block table includes fields Blockid, Isfree, Dev.
  • the PostgreSQL block storage device read and write module has the following submodules:
  • a submodule that writes data in a PostgreSQL block is a submodule that writes data in a PostgreSQL block.
  • the sub-module that allocates the PostgreSQL block allocates a PostgreSQL block to the PostgreSQL data table by using a nearby allocation policy or a hot-hot data hierarchical allocation policy, and the nearby allocation strategy is a PostgreSQL block nearest allocation policy or an idle PostgreSQL block table recording nearest allocation policy.
  • the hot-cold data table hierarchical allocation strategy is a common data table allocation strategy or a recently used data table allocation strategy.
  • the PostgreSQL block nearest allocation strategy is to find an idle PostgreSQL block to be assigned to the data table before and after the last allocated PostgreSQL block of the data table.
  • the free PostgreSQL block table record near allocation strategy is to find the first free PostgreSQL block from the idle PostgreSQL block table record, the commonly used data table allocation strategy is to preferentially allocate the data table to the faster PostgreSQL block device.
  • the recently used data table allocation strategy is to prioritize the recently used data table to a faster PostgreSQL block device for a PostgreSQL block device having two or more different read and write speeds. on;
  • the submodule of the Recycled PostgreSQL block is used to reclaim the PostgreSQL block that is no longer used by the data table, and the corresponding PostgreSQL block record is deleted from the mapping relationship table between the PostgreSQL block and the data table, and the record of the corresponding PostgreSQL block is sent to the free table.
  • the sub-module for locating the PostgreSQL block is used to locate a page in the data table to a location specified by the PostgreSQL block device;
  • the submodule for reading data in the PostgreSQL block is used to read the specified location in the specified block.
  • Fixed size data
  • the sub-module that writes the data in the PostgreSQL block is used to write data of a specified size within a specified location within the specified block.
  • the submodule that writes the data in the PostgreSQL block writes the data to the PostgreSQL block in an encrypted manner; accordingly,
  • the sub-module that reads the data in the PostgreSQL block reads the data back to the database business layer in a decrypted manner.
  • the encryption method is a method of performing storage encryption on the user password and data XOR;
  • the decryption method is a method of encrypting the user password with the data read from the PostgreSQL block and then returning it to the database service layer.
  • the Dev field in the idle PostgreSQL block table identifies different storage devices to implement capacity expansion.
  • the PostgreSQL block is the smallest unit allocated to the data table in the PostgreSQL database system, and is characterized in that the storage capacity of the PostgreSQL block is greater than 4 KB.
  • the storage capacity of the PostgreSQL block is a positive integer multiple of 8 KB.
  • the storage capacity of the PostgreSQL block is a natural multiple of 8 KB of 2 KB.
  • the storage capacity of the PostgreSQL block is 1 MB, 2 MB, 4 MB, 8 MB, 16 MB, 32 MB, 64 MB, 128 MB, 256 MB, 512 MB or 1024 MB.
  • the migration method based on the PostgreSQL block storage device of the present invention has the following beneficial effects compared with the prior art.
  • Database business and data separation As long as it is the same version of the database, it can be freely migrated in different operating systems. As long as the verification code set at the head of the data block can be directly mounted, the database can be directly mounted. It is free to migrate from different versions of Linux, and can also migrate with the Windows operating system platform.
  • the data in the database will be more secure.
  • the data in the database will be saved to the block device according to the rules we have established, which is more secure in terms of security.
  • the data will be saved in pieces and saved in multiple copies to different data nodes. In terms of single disk, it is more than 100 times.
  • the query speed and read/write speed can be greatly improved, and the speed can be increased by 10% to 20% under the same back-end storage. This improvement is very impressive for the database.
  • the PostgreSQL block, the PostgreSQL block device read/write storage module, and the PostgreSQL block storage device migration method of the present invention are further described in detail below with reference to the accompanying drawings and specific embodiments.
  • FIG. 1 is a schematic diagram of a file system read and write hierarchical structure of an operating system in the prior art.
  • FIG. 2 is a schematic diagram of a file system storage space allocation structure of an operating system in the prior art.
  • FIG. 3 is a schematic diagram of the principle of read and write of a file system head of an operating system in the prior art.
  • FIG. 4 is a schematic diagram showing the structure and principle of a PostgreSQL block, a PostgreSQL block device read/write storage module, and a migration method based on a PostgreSQL block storage device.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • the PostgreSQL block of the present invention is the smallest unit allocated to the data table in the PostgreSQL database system, and the storage capacity of the PostgreSQL block is equal to 4 MB.
  • the storage capacity of the PostgreSQL block is greater than 4 KB.
  • the storage capacity of the PostgreSQL block is a positive integer multiple of 8 KB.
  • the storage capacity of the PostgreSQL block is a natural multiple of 8 KB of 2 KB.
  • the storage capacity of the PostgreSQL block is 1 MB, 2 MB, 8 MB, 16 MB, 32 MB, 64 MB, 128 MB, 256 MB, 512 MB or 1024 MB.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the PostgreSQL block storage device read/write module of the present invention is a PostgreSQL block storage device read/write module for managing a PostgreSQL block as described above in a PostgreSQL block storage device.
  • the PostgreSQL block storage device read/write module can be architected on a PostgreSQL database system.
  • the PostgreSQL block storage device read/write module manages PostgreSQL blocks in the PostgreSQL block storage device through a mapping relationship table between PostgreSQL block-data tables and an idle PostgreSQL block table.
  • the mapping relationship table between the PostgreSQL block and the data table includes fields Relfilenode, Reltablespace, Forknum, Blockid, Blockno, and the free PostgreSQL block table includes fields Blockid, Isfree, Dev.
  • the PostgreSQL block storage device read and write module has the following submodules:
  • a submodule that writes data in a PostgreSQL block is a submodule that writes data in a PostgreSQL block.
  • the sub-module that allocates the PostgreSQL block allocates a PostgreSQL block to the PostgreSQL data table by using a nearby allocation policy or a hot-hot data hierarchical allocation policy, and the nearby allocation strategy is a PostgreSQL block nearest allocation policy or an idle PostgreSQL block table recording nearest allocation policy.
  • the hot-cold data table hierarchical allocation strategy is a common data table allocation strategy or a recently used data table allocation strategy.
  • the PostgreSQL block nearest allocation strategy is to find an idle PostgreSQL block to be assigned to the data table before and after the last allocated PostgreSQL block of the data table.
  • the free PostgreSQL block table record near allocation strategy is to find the first free PostgreSQL block from the idle PostgreSQL block table record, the commonly used data table allocation strategy is to preferentially allocate the data table to the faster PostgreSQL block device.
  • the recently used data table allocation strategy is to prioritize the recently used data table to a faster PostgreSQL block device for a PostgreSQL block device having two or more different read and write speeds. on;
  • the submodule of the Recycled PostgreSQL block is used to reclaim the PostgreSQL block that is no longer used by the data table, and the corresponding PostgreSQL block record is deleted from the mapping relationship table between the PostgreSQL block and the data table, and the record of the corresponding PostgreSQL block is sent to the free table.
  • the sub-module for locating the PostgreSQL block is used to locate a page in the data table to a location specified by the PostgreSQL block device;
  • the submodule for reading data in the PostgreSQL block is used to read data of a specified size in a specified position in the specified block;
  • the sub-module that writes the data in the PostgreSQL block is used to write data of a specified size within a specified location within the specified block.
  • the submodule that writes data in the PostgreSQL block writes the data in an encrypted manner In the PostgreSQL block; accordingly,
  • the sub-module that reads the data in the PostgreSQL block reads the data back to the database business layer in a decrypted manner.
  • the encryption method is a method of performing storage encryption on the user password and data XOR;
  • the decryption method is a method of deciphering the user password and the data read from the PostgreSQL block and then deciphering it to the database service layer.
  • the Dev field in the idle PostgreSQL block table identifies different storage devices to implement capacity expansion.
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • the present invention is based on a migration method of a PostgreSQL block storage device, and reads and writes a PostgreSQL block as described above by using a PostgreSQL block storage device read/write module as described above.
  • the driver of the PostgreSQL block storage device read/write module completes the operation of the block file, and its main tasks are:
  • the table space is located to a specified position of the specified block device, and a certain offset of the block device is located by the pageid of the table.
  • Each table in the PostgreSQL database system is assigned at least one of the PostgreSQL blocks, and the PostgreSQL block can be dynamically allocated incrementally;
  • Each PostgreSQL block can write to 512 8-KB PostgreSQL block database system pages.
  • a block device can contain an infinite number of tables.
  • a table can contain an unlimited number of PostgreSQL blocks. These block file information is stored in PostgreSQL block-data. The mapping relationship between the tables;
  • the information of all the PostgreSQL blocks of a data table can be obtained by one oid, and the PostgreSQL block information will sequentially form the entire PostgreSQL block-data table file.
  • the pageid*8k of this table is the internal bias of the table. Move, and at the same time be able to determine the first block of this block file, and thus get the position of the page we want to get in the block device.
  • the PostgreSQL block storage device In general, we split the PostgreSQL block storage device by 4MB. We only need to calculate the total number of PostgreSQL block storage devices by dividing the total capacity of the PostgreSQL block storage device by the capacity of a PostgreSQL block. This does not require scanning the PostgreSQL block storage device. This allocation time is extremely short. For example, the 2T PostgreSQL block storage device only needs to be divided into 524288 PostgreSQL blocks. We only need to add 524288 records to the free PostgreSQL block table, and the blockid can be incremented from 0--524287. Also mark isfree as true.
  • the storage space of the data table is allocated in units of 4 MB.
  • the actual occupied space of a table is allocated on demand.
  • the original SMgrRelation reln, ForkNumber forknum two parameters are located to the file system's table file modified to locate the offset of the block device.
  • PostgreSQL block-data table exists in the mapping table, we can directly locate the PostgreSQL block storage device to pageno*4*1024KB+(reln.pageid%512)*8KB. Read this 8K data.
  • the database business layer is separated from the data layer. Mount the block device directly to the new node. This upper level system error does not affect the underlying data.
  • PostgreSQL block storage device selection rules can be customized.
  • step B we are the choice of order.
  • PostgreSQL database system background storage is stored on a bare disk basis.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Human Computer Interaction (AREA)
  • Data Mining & Analysis (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'invention concerne un procédé de migration fondé sur un dispositif de mémorisation de blocs PostgreSQL qui utilise un module de lecture-écriture de dispositif de mémorisation de blocs PostgreSQL, afin d'exécuter des opérations de lecture et d'écriture vers des blocs PostgreSQL, la gestion par le module de lecture-écriture de dispositif de mémorisation de blocs PostgreSQL, au moyen d'une table de blocs PostgreSQL inactive, d'une table de relation de correspondance entre les blocs PostgreSQL et de tables de données, des blocs PostgreSQL dans le dispositif de mémorisation de blocs PostgreSQL, la copie de la table de blocs PostgreSQL inactive, de la table de relation de correspondance entre les blocs PostgreSQL et des tables de données depuis une base de données d'origine vers une nouvelle base de données, et la migration du dispositif de mémorisation de blocs PostgreSQL depuis l'ordinateur dans lequel est située la base de données d'origine vers l'ordinateur dans lequel est située la nouvelle base de données. La migration d'une base de données entre différents systèmes au moyen du procédé de migration fondé sur le dispositif de mémorisation de blocs PostgreSQL est facile et ne requiert pas de connaissance professionnelle des opérateurs. La vitesse d'interrogation et la vitesse de lecture-écriture peuvent être améliorées, les vitesses étant améliorées de 10 % à 20 % dans les mêmes conditions de mémoire principale.
PCT/CN2016/096971 2015-12-17 2016-08-26 Procédé de migration fondé sur un dispositif de mémorisation de blocs postgresql WO2017101505A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510955290 2015-12-17
CN201510955290.X 2015-12-17

Publications (1)

Publication Number Publication Date
WO2017101505A1 true WO2017101505A1 (fr) 2017-06-22

Family

ID=56987026

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/096971 WO2017101505A1 (fr) 2015-12-17 2016-08-26 Procédé de migration fondé sur un dispositif de mémorisation de blocs postgresql

Country Status (2)

Country Link
CN (1) CN105824879B (fr)
WO (1) WO2017101505A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115098492A (zh) * 2022-05-17 2022-09-23 中国人民财产保险股份有限公司 一种分布式数据库的分库方法、装置及存储介质

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105630879B (zh) * 2015-12-17 2019-03-26 深圳市华讯方舟软件技术有限公司 一种PostgreSQL块存储设备读写模块
CN105824879B (zh) * 2015-12-17 2019-06-28 深圳市华讯方舟软件技术有限公司 一种基于PostgreSQL块存储设备的迁移方法
CN105573678B (zh) * 2015-12-17 2018-11-09 深圳市华讯方舟软件技术有限公司 一种PostgreSQL块
CN106815298B (zh) * 2016-12-09 2020-11-17 中电科华云信息技术有限公司 基于块存储的分布式共享文件系统
CN111367470B (zh) * 2020-02-21 2021-09-17 苏州浪潮智能科技有限公司 分布式存储卷在线迁移方法、系统、装置及可读存储介质
CN111506685A (zh) * 2020-03-24 2020-08-07 山东省国土测绘院 一种融合制图方法、系统及电子设备
CN112035461B (zh) * 2020-06-17 2024-05-10 深圳市法本信息技术股份有限公司 数据库的表数据文件的迁移方法和系统
CN112380217B (zh) * 2020-11-17 2024-04-12 安徽鸿程光电有限公司 数据处理方法、装置、设备及介质
CN112800051A (zh) * 2020-12-28 2021-05-14 厦门市美亚柏科信息股份有限公司 一种PostGresSQL数据库删除记录的恢复方法和装置

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101009645A (zh) * 2006-12-22 2007-08-01 清华大学 基于cam的宽带网络业务流按每流排队的可扩展的装置
WO2010005447A1 (fr) * 2008-07-07 2010-01-14 Kickfire, Inc. Procédés et systèmes pour générer des plans d'interrogation qui sont compatibles pour une exécution dans un matériel
CN102243629A (zh) * 2010-05-12 2011-11-16 北京安华金和科技有限公司 一种基于多级视图和触发器的数据库透明加解密方法
CN102768672A (zh) * 2012-06-12 2012-11-07 上海方正数字出版技术有限公司 一种磁盘空间管理方法和装置
CN105573678A (zh) * 2015-12-17 2016-05-11 深圳市华讯方舟软件技术有限公司 一种PostgreSQL块
CN105630879A (zh) * 2015-12-17 2016-06-01 深圳市华讯方舟软件技术有限公司 一种PostgreSQL块存储设备读写模块
CN105824879A (zh) * 2015-12-17 2016-08-03 深圳市华讯方舟软件技术有限公司 一种基于PostgreSQL块存储设备的迁移方法

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100337220C (zh) * 2003-02-17 2007-09-12 西安三茗科技有限责任公司 一种Linux系统硬盘数据实时动态保护方法
KR100703753B1 (ko) * 2005-04-14 2007-04-06 삼성전자주식회사 파일 시스템 관리 장치 및 방법
CN101567003B (zh) * 2009-05-27 2012-05-16 清华大学 并行文件系统中资源的管理和分配方法
CN102622272A (zh) * 2012-01-18 2012-08-01 北京华迪宏图信息技术有限公司 基于集群和并行技术的海量卫星数据处理系统及处理方法
CN104462119B (zh) * 2013-09-18 2019-11-05 腾讯科技（深圳）有限公司 数据迁移方法及装置

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101009645A (zh) * 2006-12-22 2007-08-01 清华大学 基于cam的宽带网络业务流按每流排队的可扩展的装置
WO2010005447A1 (fr) * 2008-07-07 2010-01-14 Kickfire, Inc. Procédés et systèmes pour générer des plans d'interrogation qui sont compatibles pour une exécution dans un matériel
CN102243629A (zh) * 2010-05-12 2011-11-16 北京安华金和科技有限公司 一种基于多级视图和触发器的数据库透明加解密方法
CN102768672A (zh) * 2012-06-12 2012-11-07 上海方正数字出版技术有限公司 一种磁盘空间管理方法和装置
CN105573678A (zh) * 2015-12-17 2016-05-11 深圳市华讯方舟软件技术有限公司 一种PostgreSQL块
CN105630879A (zh) * 2015-12-17 2016-06-01 深圳市华讯方舟软件技术有限公司 一种PostgreSQL块存储设备读写模块
CN105824879A (zh) * 2015-12-17 2016-08-03 深圳市华讯方舟软件技术有限公司 一种基于PostgreSQL块存储设备的迁移方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115098492A (zh) * 2022-05-17 2022-09-23 中国人民财产保险股份有限公司 一种分布式数据库的分库方法、装置及存储介质

Also Published As

Publication number Publication date
CN105824879B (zh) 2019-06-28
CN105824879A (zh) 2016-08-03

Similar Documents

Publication Publication Date Title
WO2017101505A1 (fr) Procédé de migration fondé sur un dispositif de mémorisation de blocs postgresql
WO2017101478A1 (fr) Module de lecture-écriture de dispositif de stockage de bloc postgresql
Ramakrishnan et al. Azure data lake store: a hyperscale distributed file service for big data analytics
TWI778157B (zh) 固態驅動器、分散式資料儲存系統和利用鍵值儲存的方法
US11287994B2 (en) Native key-value storage enabled distributed storage system
US9047301B2 (en) Method for optimizing the memory usage and performance of data deduplication storage systems
CN106663047A (zh) 用于优化的签名比较和数据复制的系统和方法
US11301421B2 (en) Scalable multi-tier storage structures and techniques for accessing entries therein
CN103597440A (zh) 用于创建克隆文件的方法以及采用该方法的文件系统
US11775476B2 (en) Techniques for snapshotting scalable multitier storage structures
WO2017101477A1 (fr) Bloc postgresql
CN111324305B (zh) 一种分布式存储系统中数据写入/读取方法
CN113535670B (zh) 一种虚拟化资源镜像存储系统及其实现方法
US8140886B2 (en) Apparatus, system, and method for virtual storage access method volume data set recovery
CN104054071A (zh) 访问存储设备的方法和存储设备
WO2022134269A1 (fr) Procédé d'optimisation d'un moteur de pré-calcul de traitement analytique en ligne sur la base d'un stockage d'objets, et son application
US7549029B2 (en) Methods for creating hierarchical copies
WO2021068517A1 (fr) Procédé et dispositif de tri de données mémorisées
US10387384B1 (en) Method and system for semantic metadata compression in a two-tier storage system using copy-on-write
WO2022262381A1 (fr) Procédé et appareil de compression de données
US8918621B1 (en) Block address isolation for file systems
US6910214B1 (en) Method, system, and program for converting an input parameter list into an output parameter list
US11537297B1 (en) Deleting snapshot pages using sequence numbers and page lookups
US20230176921A1 (en) Application-defined storage architecture for offloading computation
Shu Storage Technology Trends and Development

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16874565

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16874565

Country of ref document: EP

Kind code of ref document: A1