História stránky

...

- Use the TREZOR COMPRESS command to compress the depository data (compression will take place quickly, as the existing data in the compressed data tables will be used). Compression will delete the original data table with uncompressed data (DATA).

• Kotva
  trezorcompressreorg trezorcompressreorg

  TrezorCompressReorg - reorganization of the depository data before compression. This parameter has a default value of 1 - in practice, it turns out that it is more efficient and faster to reorganize the data first (by an SQL command CLUSTER DATA) and then compress them. A value of 0 disables reorganization of the depository data before compression. Disabling reorganization before compression is not recommended.
  The parameter can be changed online, by the SET_OPTION TrezorCompressReorg  commandTrezorCompressReorg command.
  

• Kotva
  trezorcompresscmt trezorcompresscmt

  TrezorCompressCmt  -the parameter specifies the number of archive objects after the compression of which a COMMIT will be executed. The default value is 10. In applications with intensively archived objects (many values of one archive object in the depository ), this parameter can be reduced down to 1. Conversely, in applications with many archive objects that change infrequently, it is possible to increase the value of this parameter.
  The parameter can be changed online, by the SET_OPTION TrezorCompressCmt command.
  
  

• Kotva
  trezorcompressorder trezorcompressorder

  TrezorCompressOrder - the parameter refers to reading from depositories with compressed data. This parameter indicates whether time sorting is required when reading data from a compressed depository. Since the data is sorted during compression, it is possible to leave the parameter at 0 by default, which speeds up reading from the compressed vault (ORDER BY clause is omitted)
  The parameter can be changed online, by the SET_OPTION TrezorCompressOrder command.

...