Re: A few more opportunities to use TupleTableSlotOps fields - Mailing list pgsql-hackers

From Robert Haas
Subject Re: A few more opportunities to use TupleTableSlotOps fields
Date
Msg-id CA+TgmoZ1FRuH_K1_OnFfbNjfYv0TpCQ5Pv9BJG-cQ4WND2UGSg@mail.gmail.com
Whole thread Raw
In response to A few more opportunities to use TupleTableSlotOps fields  (Antonin Houska <ah@cybertec.at>)
Responses Re: A few more opportunities to use TupleTableSlotOps fields  (Antonin Houska <ah@cybertec.at>)
List pgsql-hackers
On Tue, May 21, 2019 at 8:02 AM Antonin Houska <ah@cybertec.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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] Unlogged tables cleanup
Next
From: Tom Lane
Date:
Subject: Re: VACUUM fails to parse 0 and 1 as boolean value