Re: tuplesort_gettuple_common() and *should_free argument

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: David Steele <david(at)pgmasters(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, hlinnaka <hlinnaka(at)iki(dot)fi>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: tuplesort_gettuple_common() and *should_free argument
Date: 2017-03-13 22:12:12
Message-ID: CAH2-Wz=RGGyrYOr95HoALzxGc4HLpisQk4OGNbZk6t4T_L2iiA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 13, 2017 at 8:23 AM, David Steele <david(at)pgmasters(dot)net> wrote:
> It's been a while since there was a new patch or any activity on this
> thread.
>
> If you need more time to produce a patch, please post an explanation for
> the delay and a schedule for the new patch. If no patch or explanation
> is is posted by 2017-03-16 AoE I will mark this submission
> "Returned with Feedback".

Apologies for the delay on this. I intend to get back to it before that time.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2017-03-13 22:35:30 Re: Performance improvement for joins where outer side is unique
Previous Message Tom Lane 2017-03-13 22:05:02 Re: [PATCH] Use $ parameters as replacement characters for pg_stat_statements