Re: A few more opportunities to use TupleTableSlotOps fields

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Antonin Houska <ah(at)cybertec(dot)at>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: A few more opportunities to use TupleTableSlotOps fields
Date: 2019-05-21 12:40:49
Message-ID: CA+TgmoZ1FRuH_K1_OnFfbNjfYv0TpCQ5Pv9BJG-cQ4WND2UGSg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 21, 2019 at 8:02 AM Antonin Houska <ah(at)cybertec(dot)at> wrote:
> Perhaps it's just a matter of taste, but I think the TupleTableSlotOps
> structure, once initialized, should be used wherever possible. At least for me
> personally, when I read the code, the particular callback function name is a
> bit disturbing wherever it's not necessary.

But it's significantly more efficient.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-05-21 13:40:22 Re: VACUUM fails to parse 0 and 1 as boolean value
Previous Message Robert Haas 2019-05-21 12:39:18 Re: [HACKERS] Unlogged tables cleanup