On Mon, Jan 23, 2017 at 1:52 PM, Haribabu Kommi
<kommi.harib...@gmail.com> wrote:
> I reviewed 0002-hash-support-alloc-free-v12.patch, some minor comments.
>
> - SH_TYPE *tb;
> - uint64 size;
> + SH_TYPE *tb;
> + uint64 size;
>
> The above change may not be required.
>
> + if (tb->alloc)
> + {
> + tb->alloc->HashFree(tb->data, tb->alloc->args);
> + pfree(tb->alloc);
> + }
>
> The above code tries to free the tb->alloc memory. In case if the user
> has provide the alloc structure to SH_CREATE function and the same
> pointer is stored in the tb structure. And in free function freeing that
> memory may cause problem.
>
> So either explicitly mentioning that the input must a palloc'ed data or
> by default allocate memory and copy the input data into allocated
> memory.I have changed as per the comments. 0002 and 0003 are changed, 0001 is still the same. -- Regards, Dilip Kumar EnterpriseDB: http://www.enterprisedb.com
0001-opt-parallelcost-refactoring-v13.patch
Description: Binary data
0002-hash-support-alloc-free-v13.patch
Description: Binary data
0003-parallel-bitmap-heap-scan-v13.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
