Re: tuplesort_gettuple_common() and *should_free argument

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Peter Geoghegan <pg(at)heroku(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, 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-04-06 21:57:56
Message-ID: CAH2-Wzn3rY2N0gTWndaApD113T+O8L6oz8cm7_F3P8y4awdoOg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

On Thu, Apr 6, 2017 at 2:50 PM, Andres Freund <andres(at)anarazel(dot)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/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2017-04-06 22:13:16 Re: Letting the client choose the protocol to use during a SASL exchange
Previous Message Peter Geoghegan 2017-04-06 21:52:30 Re: tuplesort_gettuple_common() and *should_free argument