Re: Bug in batch tuplesort memory CLUSTER case (9.6 only) - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Bug in batch tuplesort memory CLUSTER case (9.6 only)
Date
Msg-id CAM3SWZTR-v_AX_76Tikp-T=eu1XecjmJ2zME0NgRa=Y+Bi1cVA@mail.gmail.com
Whole thread Raw
In response to Re: Bug in batch tuplesort memory CLUSTER case (9.6 only)  (Peter Geoghegan <pg@heroku.com>)
Responses Re: Bug in batch tuplesort memory CLUSTER case (9.6 only)  (Noah Misch <noah@leadboat.com>)
List pgsql-hackers
On Fri, Jul 1, 2016 at 12:30 PM, Peter Geoghegan <pg@heroku.com> wrote:
> Checkout my gensort tool from github. Build the C tool with "make".
> Then, from the working directory:
>
> ./postgres_load.py -m 250 --skew --logged
> psql -c "CREATE INDEX segfaults on sort_test_skew(sortkey);"
> psql -c "CLUSTER sort_test_skew USING segfaults;"

I think that almost any CLUSTER based on an external sort would show
problems with valgrind memcheck, though. That's probably far easier.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Andreas Seltenreich
Date:
Subject: [sqlsmith] ERROR: plan should not reference subplan's variable
Next
From: Tom Lane
Date:
Subject: Re: Bad behavior from plpython 'return []'