Re: renaming ExecStoreWhateverTuple

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: renaming ExecStoreWhateverTuple
Date: 2019-03-25 15:30:30
Message-ID: CA+Tgmob1S2WH=Rch=H=vv9GJ6a7LavTV5=5zhLwYymH9D1mP=A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 25, 2019 at 11:27 AM Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Should we keep ExecStoreTuple as a compatibility macro for third party
> code?

I think that might be rather dangerous, actually, because slots now
have a type, which they didn't before. You have to use the correct
function for the kind of slot you've got.

--
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 Alvaro Herrera 2019-03-25 15:49:29 Re: renaming ExecStoreWhateverTuple
Previous Message Nikita Glukhov 2019-03-25 15:29:58 Re: [PATCH] kNN for btree