Re: Pinning a buffer in TupleTableSlot is unnecessary

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Pinning a buffer in TupleTableSlot is unnecessary
Date: 2016-11-14 17:54:38
Message-ID: CAM3SWZS_2t4SxVxBTpSwAss+q6VPO1nb9kc6eRs+-EoJ08KCbg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 14, 2016 at 9:22 AM, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
> I think that difference in the API is exactly what caught Peter by surprise
> and led to bug #14344. And I didn't see it either, until you two debugged
> it.

That is accurate, of course.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2016-11-14 17:56:28 Re: Pinning a buffer in TupleTableSlot is unnecessary
Previous Message Tom Lane 2016-11-14 17:32:53 Re: Pinning a buffer in TupleTableSlot is unnecessary