On Wed, Jun 21, 2017 at 8:57 AM, Dilip Kumar <dilipbal...@gmail.com> wrote:
> For the default partition we are only setting bound->content to
> default, but content for others key
> attributes are not initialized. But later in the code, if the content
> of the first key is RANGE_DATUM_DEFAULT then it should not access the
> next content, but I see there are some exceptions. Which can access
> uninitialized value?
I think somebody should do some testing of the existing code with
valgrind. And then apply the list-partitioning patch and this patch,
and do some more testing with valgrind. It seems to be really easy to
miss these uninitialized access problems during code review.
The Enterprise PostgreSQL Company
Sent via pgsql-hackers mailing list (email@example.com)
To make changes to your subscription: