Re: [HACKERS] No-op case in ExecEvalConvertRowtype - Mailing list pgsql-hackers

From Ashutosh Bapat
Subject Re: [HACKERS] No-op case in ExecEvalConvertRowtype
Date
Msg-id CAFjFpRfXQ+_Soh4dTP9sRjNg3q6Gf0Kw=HNSrxfTL9LTWaxWEw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] No-op case in ExecEvalConvertRowtype  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] No-op case in ExecEvalConvertRowtype  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Apr 7, 2017 at 5:06 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> So I now think it's okay to remove consideration of matching the target
> rowtype OID from the tupconvert.c functions, although we have to realize
> that that is effectively an API change for them, one which has a definite
> potential for biting third-party callers.

While I agree that we can remove indesc->tdtypeid ==
outdesc->tdtypeid, I am not sure whether it should be replaced by
!indesc->tdhasoid && !outdesc->tdhasoid. If that's required, it seems
to be a bug that needs to be fixed in earlier braches as well.

-- 
Best Wishes,
Ashutosh Bapat
EnterpriseDB Corporation
The Postgres Database Company



pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: [HACKERS] No-op case in ExecEvalConvertRowtype
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] src/interfaces/libpq shipping nmake-related Makefiles