Re: pgsql: Get rid of copy_partition_key - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: pgsql: Get rid of copy_partition_key
Date
Msg-id 20171222164756.7hpnu3dt3xhn7whh@alvherre.pgsql
Whole thread Raw
In response to Re: pgsql: Get rid of copy_partition_key  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: pgsql: Get rid of copy_partition_key  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
Seems I misremembered the whole opfuncid getting reset thing (it applies
to reading a node from string, not copying) and it was undone by
9f1255ac8593 anyway.  I don't think it makes much of a difference, but I
mention this in case you're wondering why I changed the fix_opfuncids()
call.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pgsql: Get rid of copy_partition_key
Next
From: Alvaro Herrera
Date:
Subject: Unique indexes & constraints on partitioned tables