| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: renaming ExecStoreWhateverTuple |
| Date: | 2019-03-25 16:32:56 |
| Message-ID: | 20190325163256.d6vcrt3yb2upy6yy@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2019-03-25 12:05:52 -0400, Robert Haas wrote:
> 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.
Right, but is that going to be more people that are going to be confused
by the difference between the already existing slot_ functions and the
existing camel-cased stuff?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-03-25 16:33:38 | Re: renaming ExecStoreWhateverTuple |
| Previous Message | Robert Haas | 2019-03-25 16:11:33 | Re: Error message inconsistency |