| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: renaming ExecStoreWhateverTuple |
| Date: | 2019-03-25 16:05:52 |
| Message-ID: | CA+TgmoZGjahuhAn8DZje1Z_BB6CGK_y4=7p8M=zFBoTiKNbxgw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 25, 2019 at 11:57 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
> I think I might go for slot_store_heap_tuple etc, given that a lot of
> those accessors have been slot_ for about ever. What do you think?
I don't have a super-strong feeling about it, although changing the
case convention might confuse a few people.
Maybe we don't really need the word "tuple". Like we could just make
it slot_store_heap() or SlotStoreHeap(). A slot can only store a
tuple, after all.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2019-03-25 16:09:30 | Re: [HACKERS] Re: [COMMITTERS] pgsql: Remove pgbench "progress" test pending solution of its timing is (fwd) |
| Previous Message | Andres Freund | 2019-03-25 15:57:02 | Re: renaming ExecStoreWhateverTuple |