Re: [HACKERS] Custom compression methods
От | Michael Paquier |
---|---|
Тема | Re: [HACKERS] Custom compression methods |
Дата | |
Msg-id | CAB7nPqSfuxBnsJs4a04M+GZF1AUQoAgTt989n3oJOvGrZS-xXg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] Custom compression methods (Tomas Vondra <tomas.vondra@2ndquadrant.com>) |
Список | pgsql-hackers |
On Thu, Nov 30, 2017 at 8:30 AM, Tomas Vondra <tomas.vondra@2ndquadrant.com> wrote: > On 11/28/2017 02:29 PM, Ildus Kurbangaliev wrote: >> On Mon, 27 Nov 2017 18:20:12 +0100 >> Tomas Vondra <tomas.vondra@2ndquadrant.com> wrote: >> >>> I guess the trick might be -DRANDOMIZE_ALLOCATED_MEMORY (I first >>> tried without it, and it seemed working fine). If that's the case, >>> I bet there is a palloc that should have been palloc0, or something >>> like that. >> >> Thanks, that was it. I've been able to reproduce this bug. The >> attached patch should fix this bug and I've also added recompression >> when tuples moved to the relation with the compressed attribute. >> > > I've done many tests with fulltext search on the mail archive, using > different compression algorithm, and this time it worked fine. So I can > confirm v7 fixes the issue. Moved to next CF. -- Michael
В списке pgsql-hackers по дате отправления: