Re: [HACKERS] Custom compression methods
| От | Alvaro Herrera |
|---|---|
| Тема | Re: [HACKERS] Custom compression methods |
| Дата | |
| Msg-id | 20201124192031.GA22772@alvherre.pgsql обсуждение исходный текст |
| Ответ на | Re: [HACKERS] Custom compression methods (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: [HACKERS] Custom compression methods
|
| Список | pgsql-hackers |
On 2020-Nov-24, Tom Lane wrote: > Robert Haas <robertmhaas@gmail.com> writes: > > Oh, I thought it had been suggested in previous discussions that these > > should be treated as access methods rather than inventing a whole new > > concept just for this, and it seemed like a good idea to me. I guess I > > missed the fact that the patch wasn't doing it that way. Hmm. > > FWIW, I kind of agree with Robert's take on this. Heap and index AMs > are pretty fundamentally different animals, yet we don't have a problem > sticking them in the same catalog. I think anything that is related to > storage access could reasonably go into that catalog, rather than > inventing a new one. Right -- Something like amname=lz4, amhandler=lz4handler, amtype=c. The core code must of course know how to instantiate an AM of type 'c' and what to use it for. https://postgr.es/m/20171213151818.75a20259@postgrespro.ru
В списке pgsql-hackers по дате отправления: