[HACKERS] COMPRESS VALUES feature request
От | Erez Segal |
---|---|
Тема | [HACKERS] COMPRESS VALUES feature request |
Дата | |
Msg-id | CAPo0pRFeB7vbcKqHAN55geW9tYmj+MG_HVugVkSp4KfHvphtmA@mail.gmail.com обсуждение исходный текст |
Ответы |
Re: [HACKERS] COMPRESS VALUES feature request
|
Список | pgsql-hackers |
Hi,
Following a discussion in the IRC channel, I'd like to suggest a feature request to the ToDo WIKI page.
The use case is having a column with strings/floats, where some values are very common and can be compressed, while many other values are unique, making a lookup table not efficient.
It can be part of a column definition, set in CREATE TABLE/ALTER TABLE
e.g. field VARCHAR(255) COMPRESS (NULL, 'EREZ', 'SEGAL')
The feature exists in TeraData:
https://community.teradata.com/t5/Database/how-does-compress-work-in-tables/td-p/13950
https://community.teradata.com/t5/Database/how-does-compress-work-in-tables/td-p/13950
In the IRC channel - johto suggested an implementation:
<johto> if you want to get really fancy you could have two columns where only one of set; one would be the value (if reasonably unique) and the other the id (if not)
<johto> if you want to get really fancy you could have two columns where only one of set; one would be the value (if reasonably unique) and the other the id (if not)
I'd like to add that an ENUM can be used instead of the id+lookup table in the 2nd column for non unique values.
В списке pgsql-hackers по дате отправления: