Re: [HACKERS] Custom compression methods
От | Robert Haas |
---|---|
Тема | Re: [HACKERS] Custom compression methods |
Дата | |
Msg-id | CA+TgmoZqJYP+othk0c-r6acjVWWvBoxkWm5eHLUE=8VyezQKKw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] Custom compression methods (Alexander Korotkov <a.korotkov@postgrespro.ru>) |
Ответы |
Re: [HACKERS] Custom compression methods
|
Список | pgsql-hackers |
On Mon, Dec 11, 2017 at 1:06 PM, Alexander Korotkov <a.korotkov@postgrespro.ru> wrote: > OK, but NOTICE that presumably unexpected table rewrite takes place could be > still useful. I'm not going to complain too much about that, but I think that's mostly a failure of expectation rather than a real problem. If the documentation says what the user should expect, and they expect something else, tough luck for them. > Also we probably should add some view that will expose compression methods > whose are currently preserved for columns. So that user can correctly > construct SET COMPRESSION query that doesn't rewrites table without digging > into internals (like directly querying pg_depend). Yes. I wonder if \d or \d+ can show it somehow. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: