Re: [HACKERS] tuplesort_gettuple_common() and *should_free argument - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: [HACKERS] tuplesort_gettuple_common() and *should_free argument
Date
Msg-id CAH2-Wzn3rY2N0gTWndaApD113T+O8L6oz8cm7_F3P8y4awdoOg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] tuplesort_gettuple_common() and *should_free argument  (Andres Freund <andres@anarazel.de>)
Responses Re: [HACKERS] tuplesort_gettuple_common() and *should_free argument  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Thu, Apr 6, 2017 at 2:50 PM, Andres Freund <andres@anarazel.de> wrote:
> Pushed with very minor wording changes.

This had a typo:

+ * If copy is true, the slot receives a copied tuple that'll that will stay


-- 
Peter Geoghegan

VMware vCenter Server
https://www.vmware.com/



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: [HACKERS] tuplesort_gettuple_common() and *should_free argument
Next
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Letting the client choose the protocol to use during aSASL exchange