Re: [HACKERS] [COMMITTERS] pgsql: Fix a bug in how we generatepartition constraints.
От
Amit Langote
Тема
Re: [HACKERS] [COMMITTERS] pgsql: Fix a bug in how we generatepartition constraints.
Дата
Msg-id
9ce97382-54c8-deb3-9ee9-a2ec271d866b@lab.ntt.co.jp
Ответ на
Список
Дерево обсуждения
[HACKERS] Re: [COMMITTERS] pgsql: Fix a bug in how we generate partitionconstraints. Alvaro Herrera <alvherre@2ndquadrant.com>
Re: [HACKERS] [COMMITTERS] pgsql: Fix a bug in how we generate partition constraints. Robert Haas <robertmhaas@gmail.com>
Re: [HACKERS] [COMMITTERS] pgsql: Fix a bug in how we generatepartition constraints. Amit Langote <amitlangote09@gmail.com>
Re: [HACKERS] [COMMITTERS] pgsql: Fix a bug in how we generatepartition constraints. Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
On 2017/01/14 13:36, Amit Langote wrote: > On Sat, Jan 14, 2017 at 6:10 AM, Robert Haas wrote: >> On Fri, Jan 13, 2017 at 3:09 PM, Alvaro Herrera 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
В списке pgsql-hackers по дате отправления
От: Michael Paquier
Дата:
От: Michael Paquier
Дата: