Re: [HACKERS] [COMMITTERS] pgsql: Fix a bug in how we generatepartition constraints. - Mailing list pgsql-hackers

From Amit Langote
Subject Re: [HACKERS] [COMMITTERS] pgsql: Fix a bug in how we generatepartition constraints.
Date
Msg-id 9ce97382-54c8-deb3-9ee9-a2ec271d866b@lab.ntt.co.jp
Whole thread Raw
In response to Re: [HACKERS] [COMMITTERS] pgsql: Fix a bug in how we generatepartition constraints.  (Amit Langote <amitlangote09@gmail.com>)
List pgsql-hackers
On 2017/01/14 13:36, Amit Langote wrote:
> On Sat, Jan 14, 2017 at 6:10 AM, Robert Haas <robertmhaas@gmail.com> wrote:
>> On Fri, Jan 13, 2017 at 3:09 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
>>>
>>> I'm just saying that the problem at hand is already solved for a related
>>> feature, so ISTM this new code should use the recently added routine
>>> rather than doing the same thing in a different way.
>>
>> Oh, I see.  Amit, thoughts?
> 
> Hm, perhaps.  The code in map_partition_varattnos() that creates the
> map could be replaced by a call to the new
> convert_tuples_by_name_map().  In fact, it could even have used the
> old version of it (convert_tuples_by_name()).  I guess I just aped
> what other callers of map_variable_attnos() were doing, which is to
> generate the map themselves (not that they ought to be changed to use
> convert_tuples_by_name_map).
> 
> I will send a patch at my earliest convenience. Thanks to Alvaro for
> pointing that out.

And here is the patch.

Thanks,
Amit

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Patch to implement pg_current_logfile() function
Next
From: Michael Paquier
Date:
Subject: Re: [HACKERS] An isolation test for SERIALIZABLE READ ONLY DEFERRABLE