| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Get rid of copy_partition_key |
| Date: | 2017-12-22 16:47:56 |
| Message-ID: | 20171222164756.7hpnu3dt3xhn7whh@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-12-22 17:08:54 | pgsql: Disallow UNION/INTERSECT/EXCEPT over no columns. |
| Previous Message | Alvaro Herrera | 2017-12-22 16:24:19 | Re: pgsql: Get rid of copy_partition_key |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2017-12-22 21:29:21 | Unique indexes & constraints on partitioned tables |
| Previous Message | Alvaro Herrera | 2017-12-22 16:24:19 | Re: pgsql: Get rid of copy_partition_key |