Skip to content
Snippets Groups Projects
  • Tom Lane's avatar
    6edd2b4a
    Switch over to using our own qsort() all the time, as has been proposed · 6edd2b4a
    Tom Lane authored
    repeatedly.  Now that we don't have to worry about memory leaks from
    glibc's qsort, we can safely put CHECK_FOR_INTERRUPTS into the tuplesort
    comparators, as was requested a couple months ago.  Also, get rid of
    non-reentrancy and an extra level of function call in tuplesort.c by
    providing a variant qsort_arg() API that passes an extra void * argument
    through to the comparison routine.  (We might want to use that in other
    places too, I didn't look yet.)
    6edd2b4a
    History
    Switch over to using our own qsort() all the time, as has been proposed
    Tom Lane authored
    repeatedly.  Now that we don't have to worry about memory leaks from
    glibc's qsort, we can safely put CHECK_FOR_INTERRUPTS into the tuplesort
    comparators, as was requested a couple months ago.  Also, get rid of
    non-reentrancy and an extra level of function call in tuplesort.c by
    providing a variant qsort_arg() API that passes an extra void * argument
    through to the comparison routine.  (We might want to use that in other
    places too, I didn't look yet.)