You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 27, 2019. It is now read-only.
Current catalog::ColumnCatalogObject class and pg_attribute table don't have column length information, although the catalog::Column class has it. Due to this, the checkpoints can't recover the catalog::Column from pg_attribute table.
The text was updated successfully, but these errors were encountered:
@a6802739 This issue has already been implemented in PR #1383 (now reviewing). Could you try other issues? column_offset means a head location of the column in the table. It seems to be used for storage management to recognize where the column data is in the tuple. For example, assuming that a table has two columns (id interger, value varchar(36)), then id's offset is 0, and value's offset is 4.
Current catalog::ColumnCatalogObject class and pg_attribute table don't have column length information, although the catalog::Column class has it. Due to this, the checkpoints can't recover the catalog::Column from pg_attribute table.
The text was updated successfully, but these errors were encountered: