| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| 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 15:49:29 |
| Message-ID: | 20190325154929.GA24442@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-Mar-25, Robert Haas wrote:
> 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.
Ah, right. I was thinking of assuming that the un-updated third-party
code would always have a slot of type heap, but of course that's not
guaranteed.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-03-25 15:57:02 | Re: renaming ExecStoreWhateverTuple |
| Previous Message | Robert Haas | 2019-03-25 15:30:30 | Re: renaming ExecStoreWhateverTuple |